CVE-2025-40692
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSQL Injection in Online Fire Reporting System v1.2 by PHPGurukul. This vulnerability allows an attacker to retrieve, create, update and delete database via 'requestid' parameter in the endpoint '/ofrs/details.php'.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Online Fire Reporting System v1.2 contains a SQL injection vulnerability in the 'requestid' parameter of the /ofrs/details.php endpoint. Attackers can inject arbitrary SQL queries through this parameter, enabling full database compromise including unauthorized read, create, update, and delete operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed version of Online Fire Reporting SystemCheck for version indicators in the application - look for version.php, a README file, or check the HTML source for version comments. Common locations include the root directory, /includes/ folder, or the page footer.Affected if The installed version is 1.2 (exact match)
-
Verify the presence of details.phpLocate the details.php file in the /ofrs/ directory of your web server. Check the document root for an 'ofrs' subdirectory containing details.php.Affected if The file /ofrs/details.php exists in the web root
-
Inspect the requestid parameter handling in details.phpOpen details.php and examine how the 'requestid' GET parameter is used in SQL queries. Look for direct string concatenation or lack of prepared statements when building queries.Affected if The code uses direct string interpolation or concatenation with the requestid parameter without parameterized queries
-
Confirm the application is network-accessibleCheck if the /ofrs/ directory is accessible over the network. Verify the web server configuration allows access to this endpoint.Affected if The vulnerable endpoint is reachable from the network (not localhost-only or firewalled)
-
Check database user privilegesExamine the database configuration file (often db_connect.php or config.php in the application root) to determine what database user credentials the application uses.Affected if The application connects to the database with a user that has broad privileges (not read-only or restricted)
You are affected if you are running version 1.2, the details.php file exists with the vulnerable requestid parameter, and that endpoint is accessible without proper SQL prepared statement handling.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement parameterized queries (prepared statements) for the requestid parameter in details.php to prevent SQL injection, combined with input validation and least-privilege database accounts.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40692 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-40692 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data