Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2025-68434 is a high-severity CSRF (CWE-352) vulnerability in Opensourcepos Open Source Point Of Sale. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Internal Defacement (T1491.001); ranked at the 20th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-23 (Session Authenticity) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-68434 is a Cross-Site Request Forgery (CSRF) vulnerability, classified under CWE-352, affecting the Open Source Point of Sale (opensourcepos) application. This web-based point-of-sale system, written in PHP using the CodeIgniter framework, explicitly disabled its CSRF protection mechanism in the filter configuration starting from version 3.4.0 and prior to version 3.4.2. As a result, the application processes state-changing POST requests without verifying a valid CSRF token, exposing it to unauthorized actions.
An unauthenticated remote attacker can exploit this vulnerability by hosting a malicious web page. If a logged-in administrator visits the page, their browser is tricked into sending unauthorized POST requests to the opensourcepos application. A successful exploit silently creates a new Administrator account with full privileges, enabling complete system takeover and compromising confidentiality, integrity, and availability. The vulnerability has a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), highlighting its high severity due to network accessibility and low complexity, though it requires user interaction.
The vulnerability is patched in version 3.4.2, which re-enables the CSRF filter in app/Config/Filters.php and addresses related AJAX race conditions through adjusted token regeneration settings. As a workaround, administrators can manually re-enable the CSRF filter by uncommenting the relevant line in app/Config/Filters.php, but this is not recommended without the full patch, as it may break functionality in the Sales module due to token synchronization issues. Official details are available in the GitHub security advisory (GHSA-wjm4-hfwg-5w5r), pull request #4349, and the fixing commit d575c8da9a1d7af8313a1e758e000e243f5614ef.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-204014
Vulnerability Data
Open Source Point of Sale (opensourcepos) is a web based point of sale application written in PHP using CodeIgniter framework. Starting in version 3.4.0 and prior to version 3.4.2, a Cross-Site Request Forgery (CSRF) vulnerability exists in the application's filter…
more
configuration. The CSRF protection mechanism was **explicitly disabled**, allowing the application to process state-changing requests (POST) without verifying a valid CSRF token. An unauthenticated remote attacker can exploit this by hosting a malicious web page. If a logged-in administrator visits this page, their browser is forced to send unauthorized requests to the application. A successful exploit allows the attacker to silently create a new Administrator account with full privileges, leading to a complete takeover of the system and loss of confidentiality, integrity, and availability. The vulnerability has been patched in version 3.4.2. The fix re-enables the CSRF filter in `app/Config/Filters.php` and resolves associated AJAX race conditions by adjusting token regeneration settings. As a workaround, administrators can manually re-enable the CSRF filter in `app/Config/Filters.php` by uncommenting the protection line. However, this is not recommended without applying the full patch, as it may cause functionality breakage in the Sales module due to token synchronization issues.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.3.2V3.5.1V10.2.1
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.
Protecting session authenticity prevents attackers from replaying or forging authenticated requests via the victim's browser.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require anti-CSRF controls such as tokens or SameSite attributes.