CVE-2025-40687
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 'mobilenumber', 'teamleadname' and 'teammember' parameters in the endpoint '/ofrs/admin/add-team.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 confidenceSQL injection vulnerability in the Online Fire Reporting System v1.2 allows remote attackers to execute arbitrary SQL commands via the 'mobilenumber', 'teamleadname', and 'teammember' parameters in the /ofrs/admin/add-team.php endpoint. The critical severity (CVSS 9.8) indicates unauthenticated attackers can retrieve, create, update, and delete database contents.
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.
-
Verify the installed version of Online Fire Reporting SystemCheck your web root for version files, readme files, or check the admin dashboard for a version display. Common locations: /ofrs/version.php, /ofrs/admin/index.php, or check the footer of admin pages.Affected if The version is exactly 1.2 (the only affected version listed)
-
Confirm the vulnerable endpoint existsCheck if the file /ofrs/admin/add-team.php exists in your web directory by listing the directory or attempting to access it via HTTP.Affected if The file exists and is accessible via web (unauthenticated access is possible)
-
Inspect add-team.php for the vulnerable parametersOpen /ofrs/admin/add-team.php and search for usage of 'mobilenumber', 'teamleadname', and 'teammember' parameters in SQL queries. Look for direct string concatenation in SELECT/INSERT/UPDATE statements without prepared statements or binding.Affected if The code contains direct SQL queries using these parameters without parameterized queries or input sanitization
-
Check if the application database user has excessive privilegesReview the database connection configuration and verify what privileges the application database user has. Check if it can access sensitive tables beyond what's needed for the application.Affected if The database user has privileges beyond what the application requires (like DROP, GRANT, or access to multiple databases)
You are affected if you are running version 1.2 and the add-team.php file exists with unauthenticated SQL query handling for the mobilenumber, teamleadname, or teammember parameters.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements for the affected 'mobilenumber', 'teamleadname', and 'teammember' parameters in add-team.php, and audit similar endpoints for identical vulnerabilities.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40687 — 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-40687 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