dbcve.org
Online Fire Reporting SystemApplication · Phpgurukul

CVE-2025-40691

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
SQL Injection in Online Fire Reporting System v1.2 by PHPGurukul. This vulnerability allows an attacker to retrieve, create, update and delete database via  'todate' parameter in the endpoint '/ofrs/admin/bwdates-report-result.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 confidence

SQL injection vulnerability in the Online Fire Reporting System v1.2 allows unauthenticated attackers to inject arbitrary SQL commands through the 'todate' parameter in the /ofrs/admin/bwdates-report-result.php endpoint. The critical CVSS score of 9.8 indicates complete database compromise is possible, enabling data exfiltration, modification, or deletion.

MitigationImplement parameterized queries (prepared statements) for all database queries in the affected endpoint, particularly for the 'todate' parameter. Apply strict input validation and sanitize all user-supplied data before database queries. Restrict network access to the admin panel as an interim measure.

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
Online Fire Reporting SystemApplication
Affected:= 1.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the vulnerable PHP file
    Search the web root directory for the file /ofrs/admin/bwdates-report-result.php. Check if this file exists on the server.
    Affected if The file exists in the web-accessible directory structure.
  2. Identify the installed version
    Check for a version file, readme, or changelog in the application root that indicates the version number. Compare against version 1.2.
    Affected if The installed version is exactly 1.2 (the only affected version listed).
  3. Verify the 'todate' parameter is accepted
    Review the source code of bwdates-report-result.php to confirm it accepts a 'todate' GET or POST parameter and uses it in a database query without proper sanitization or prepared statements.
    Affected if The code contains a direct SQL query incorporating the 'todate' parameter without parameterized queries.
  4. Confirm admin panel is network-accessible
    Attempt to access the /ofrs/admin/ directory or the specific endpoint from an unauthorized network location. Check if the application has any IP-based access restrictions.
    Affected if The endpoint /ofrs/admin/bwdates-report-result.php is reachable from untrusted networks without authentication.
  5. Check database user privileges
    Review the database configuration file (commonly config.php or db.php in the application root) to determine the privileges of the database account used by the application.
    Affected if The application database user has elevated privileges (e.g., DROP, DELETE, or extensive GRANT options) enabling complete database compromise.

If the Online Fire Reporting System version 1.2 is installed with the bwdates-report-result.php file accessible and the 'todate' parameter used unsafely in SQL queries, the environment is affected by this SQL injection vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries (prepared statements) for all database queries in the affected endpoint, particularly for the 'todate' parameter. Apply strict input validation and sanitize all user-supplied data before database queries. Restrict network access to the admin panel as an interim measure.

Fix this in Online Fire Reporting System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-40691 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-40691 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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