CVE-2025-68147
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-17

Last updated on: 2025-12-18

Assigner: GitHub, Inc.

Description
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 Stored Cross-Site Scripting (XSS) vulnerability exists in the "Return Policy" configuration field. The application does not properly sanitize user input before saving it to the database or displaying it on receipts. An attacker with access to the "Store Configuration" (such as a rogue administrator or an account compromised via the separate CSRF vulnerability) can inject malicious JavaScript payloads into this field. These payloads are executed in the browser of any user (including other administrators and sales staff) whenever they view a receipt or complete a transaction. This can lead to session hijacking, theft of sensitive data, or unauthorized actions performed on behalf of the victim. The vulnerability has been patched in version 3.4.2 by ensuring the output is escaped using the `esc()` function in the receipt template. As a temporary mitigation, administrators should ensure the "Return Policy" field contains only plain text and strictly avoid entering any HTML tags. There is no code-based workaround other than applying the patch.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-17
Last Modified
2025-12-18
Generated
2026-05-07
AI Q&A
2025-12-18
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
opensourcepos open_source_point_of_sale From 3.4.0 (inc) to 3.4.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the Open Source Point of Sale application versions 3.4.0 up to but not including 3.4.2. It occurs in the 'Return Policy' configuration field, where user input is not properly sanitized before being saved to the database or displayed on receipts. An attacker with access to the 'Store Configuration' (such as a rogue administrator or someone who has compromised an account via a separate CSRF vulnerability) can inject malicious JavaScript code into this field. This malicious code executes in the browsers of users who view receipts or complete transactions, potentially leading to session hijacking, theft of sensitive data, or unauthorized actions performed on behalf of the victim.


How can this vulnerability impact me? :

The vulnerability can impact you by allowing attackers to execute malicious JavaScript in the browsers of users viewing receipts or completing transactions. This can result in session hijacking, theft of sensitive data, or unauthorized actions performed on behalf of the victim, potentially compromising user accounts and sensitive business information.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by inspecting the "Return Policy" configuration field in the Open Source Point of Sale application for any malicious JavaScript code or HTML tags. Since the vulnerability involves stored XSS in this field, checking the database entries or the configuration settings for suspicious script tags or unusual content can help identify exploitation. There are no specific commands provided to detect this vulnerability on the network or system.


What immediate steps should I take to mitigate this vulnerability?

Immediate steps to mitigate this vulnerability include ensuring that the "Return Policy" field contains only plain text and strictly avoiding entering any HTML tags. Administrators should review and sanitize this field to remove any potentially malicious scripts. The only code-based fix is to upgrade to version 3.4.2 or later, where the vulnerability is patched by escaping output using the `esc()` function in the receipt template.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability allows attackers to execute malicious scripts that can lead to session hijacking and theft of sensitive data. Such unauthorized access and data breaches can result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and ensuring data integrity. Therefore, this vulnerability poses a risk to compliance with these standards by potentially exposing sensitive user data and enabling unauthorized actions. [2, 3]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart