CVE-2025-9923
BaseFortify
Publication date: 2025-09-03
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 |
|---|---|---|
| campcodes | sales_and_inventory_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-9923 is a cross-site scripting (XSS) vulnerability in Campcodes Grocery Sales and Inventory System version 1.0. It occurs due to improper validation and output encoding of the 'page' parameter in the /index.php file (specifically in pages like receiving, categories, and inventory). This flaw allows attackers to inject malicious JavaScript code that executes in the victim's browser, enabling unauthorized script execution. [1, 2, 3, 4, 5]
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute arbitrary JavaScript in a victim's browser, potentially leading to theft of sensitive information such as cookies and session tokens, unauthorized actions performed on behalf of the user, defacement of web pages, redirection to malicious sites, and possibly gaining control over the victim's browser. Exploitation does not require authentication and can be launched remotely, but requires some user interaction. [1, 2, 3, 4, 5]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'page' parameter in the /index.php URL for cross-site scripting (XSS) injection. One approach is to inject a simple XSS payload such as <script>alert('xss')</script> into the 'page' parameter and observe if the script executes in the browser. For example, you can use curl or a browser to access URLs like: http://yourserver/index.php?page=<script>alert('xss')</script>. Additionally, Google dorking can be used to identify vulnerable targets by searching for "inurl:index.php". There are no specific network commands provided, but manual or automated web application scanning tools that test for XSS in URL parameters can be used. [4, 5]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement proper output encoding of the 'page' parameter based on context (HTML, JavaScript, etc.) to prevent script execution. 2) Enforce strict input validation and filtering to allow only expected input formats and reject or escape malicious content such as script tags. 3) Deploy a strict Content Security Policy (CSP) to restrict script sources and prevent execution of unauthorized scripts. 4) Set HttpOnly and Secure flags on cookies to protect against theft via JavaScript. 5) Conduct regular security audits to detect and fix XSS and other vulnerabilities promptly. If possible, consider replacing the affected product with a secure alternative. [5]