CVE-2025-40696
BaseFortify
Publication date: 2025-09-11
Last updated on: 2025-09-12
Assigner: Spanish National Cybersecurity Institute, S.A. (INCIBE)
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| phpgurukul | online_fire_reporting_system | 1.2 |
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. |
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 Online Fire Reporting System v1.2 by PHPGurukul. It occurs because the system does not properly validate user inputs for the 'fullname', 'location', and 'message' parameters sent via POST to the '/ofrs/reporting.php' endpoint. An attacker can exploit this by sending a specially crafted query that gets stored and later executed in the context of an authenticated user, potentially allowing the attacker to steal the user's session cookie. [1]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing a remote attacker to execute malicious scripts in your browser when you are authenticated on the Online Fire Reporting System. This can lead to theft of your session cookies, which may allow the attacker to hijack your account and perform unauthorized actions on your behalf. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this stored XSS vulnerability involves testing the vulnerable parameters ('fullname', 'location', 'message') at the '/ofrs/reporting.php' endpoint by sending specially crafted POST requests containing typical XSS payloads (e.g., <script>alert(1)</script>) and observing if the payload is stored and executed upon retrieval. Network detection could include monitoring HTTP POST requests to '/ofrs/reporting.php' with suspicious script tags in these parameters. Specific commands are not provided in the available resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable application to trusted users only, educating authenticated users about the risk of clicking on suspicious links, and monitoring for suspicious activity. Since no patch or solution has been reported yet, applying input validation and output encoding on the affected parameters ('fullname', 'location', 'message') is recommended as a best practice. Additionally, consider implementing web application firewall (WAF) rules to block malicious payloads targeting these parameters. [1]