Home/CVE/Open Source Point of Sale (opensourcepos) is a web based point of sale application written in PHP using CodeIgniter fram
CVE
CVE-2026-337301
Open Source Point of Sale (opensourcepos) is a web based point of sale application written in PHP using CodeIgniter fram
Open Source Point of Sale (opensourcepos) is a web based point of sale application written in PHP using CodeIgniter framework. Prior to version 3.4.2, an Insecure Direct Object Reference (IDOR) vulnerability allows an authenticated low-privileged user to access the password change functionality of other users, including administrators, by manipulating the employee_id parameter. The application does not verify object ownership or enforce authorization checks.
Version 3.4.2 adds object-level authorization checks to validate that the current user owns the employee_id being accessed.
MEDIUM · CVSS 6.5
EPSS 0.00015
EPSS exploitation odds0.01% · top 96%
Schedule remediation
- Public exploit or PoC is available
No Sigma yet — build one →
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2026-33730, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
EPSS exploitation probability
0.01%
Top 96%odds of exploitation in the next 30 days
CVSS metric silhouette
shape grows toward worst-case
SSVC triage · cisa-vulnrichment
Exploitation
poc
Automatable
no
Tech impact
partial
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Impact - what breaks
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
VECTOR
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:NLifecycle
- 27 Mar 2026Published to NVD
- 01 Apr 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
⚠
Public Exploits & PoCs
1These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted. Signed-in users mark whether it works, rate 1-10, and can report malware with a required reason that becomes a public comment.
Works?
no reports yet
Rating
◆
ATT&CK techniques
1Techniques this CVE enables - linked via CWE → CAPEC → ATT&CK. Pills with a solid outline are named directly in ATT&CK or Nuclei templates (high confidence); the others are linked through weakness mappings.
▤ Build a SIEM detection for these techniques⬡
Weakness Classification
▤
Affected Products & Versions
1▤
Related CVEs
8CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row. Not a guess.
CVE-2012-5571
A flaw was found in OpenStack Keystone. This vulnerability allows remote authent...
same CWE-639
MEDIUM
CVE-2014-8356
The web administrative portal in Zhone zNID 2426A before S3.0.501 allows remote ...
same CWE-639
HIGH
CVE-2016-20033
Wowza Streaming Engine 4.5.0 contains a local privilege escalation vulnerability...
same CWE-639
HIGH
CVE-2017-0882
Multiple versions of GitLab expose sensitive user credentials when assigning a u...
same CWE-639
MEDIUM
CVE-2025-68147
Open Source Point of Sale (opensourcepos) is a web based point of sale applicati...
same product
HIGH
CVE-2025-68434
Open Source Point of Sale (opensourcepos) is a web based point of sale applicati...
same product
HIGH
CVE-2025-68658
Open Source Point of Sale (opensourcepos) is a web based point of sale applicati...
same product
MEDIUM
CVE-2026-32888
Open Source Point of Sale is a web based point-of-sale application written in PH...
same product
HIGH
🔗
References & Sources
1Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.