CVE-2025-10065
BaseFortify
Publication date: 2025-09-07
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| facebook-kimmymatillano | point_of_sale_system | 1.0 |
Helpful Resources
Exploitability
| 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. |
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-10065 is a Cross-Site Scripting (XSS) vulnerability in itsourcecode POS Point of Sale System version 1.0. It exists in the file /inventory/main/vendors/datatables/unit_testing/templates/dom_data_th.php, where the 'scripts' parameter is not properly sanitized. This allows remote attackers to inject malicious web scripts or HTML code, which can execute in the context of the affected application when a user interacts with it. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing remote attackers to execute malicious scripts in your application without authentication. This can lead to data integrity issues, as attackers can manipulate the content displayed to users. Exploitation requires user interaction and can be done easily using publicly available exploits. However, it does not impact confidentiality or availability directly. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by searching for the vulnerable URL pattern using Google dorking with the query `inurl:inventory/main/vendors/datatables/unit_testing/templates/dom_data_th.php`. Additionally, checking web server logs for requests containing the 'scripts' parameter with suspicious or script-like input may help identify exploitation attempts. Since the vulnerability involves cross-site scripting via the 'scripts' parameter, manual testing or automated scanning tools targeting this parameter for XSS payloads can also be used. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected component or product with an alternative that does not contain this vulnerability. Since no known mitigations or countermeasures have been published, avoiding use of the vulnerable file or disabling the affected functionality may reduce risk. Additionally, applying web application firewalls (WAF) rules to block malicious scripts targeting the 'scripts' parameter can help mitigate exploitation attempts until a patch or fix is available. [2]