dbcve.org
Online Fire Reporting SystemApplication · Phpgurukul

CVE-2025-40690

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 'teamid' parameter in the endpoint '/ofrs/admin/edit-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 confidence

SQL injection vulnerability in the 'teamid' parameter of /ofrs/admin/edit-team.php allows unauthenticated remote attackers to execute arbitrary SQL commands, potentially enabling full database compromise including retrieval, creation, update, and deletion of data.

MitigationReplace dynamic SQL queries with parameterized queries (prepared statements) for all database operations on the 'teamid' parameter, or implement stored procedures with strict input validation and least-privilege database accounts.

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. Confirm the application is installed
    Locate the Online Fire Reporting System by searching for the 'ofrs' directory or 'edit-team.php' file in the web root. Check for the presence of the Phpgurukul application structure.
    Affected if The application directory /ofrs/ exists on the server and is accessible via web.
  2. Identify the installed version
    Check for a version file, README, or any file containing version information within the application root. Look for 'version', '1.2', or 'Phpgurukul' strings in source files.
    Affected if The installed version is exactly 1.2 as indicated in the affected versions.
  3. Locate the vulnerable script
    Verify that /ofrs/admin/edit-team.php exists on the filesystem. This is the specific file containing the SQL injection vulnerability.
    Affected if The file /ofrs/admin/edit-team.php is present in the web directory.
  4. Verify the teamid parameter is processed
    Open edit-team.php and search for occurrences of 'teamid' in the code. Check if this parameter is used directly in SQL queries without apparent sanitization, prepared statements, or parameter binding.
    Affected if The code contains SQL queries that incorporate the 'teamid' parameter without using parameterized queries or input validation.
  5. Check unauthenticated access to the admin endpoint
    Attempt to access /ofrs/admin/edit-team.php directly via HTTP request without logging in. Verify if the endpoint is accessible to unauthenticated users.
    Affected if The vulnerable script is accessible without authentication, allowing unauthenticated SQL injection.

If the Phpgurukul Online Fire Reporting System version 1.2 is installed, the vulnerable edit-team.php file exists, and the teamid parameter is processed in SQL queries without parameterized preparation, the environment is affected by this CVE.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries (prepared statements) for all database operations on the 'teamid' parameter, or implement stored procedures with strict input validation and least-privilege database accounts.

Recommended fix Moderate confidence

Latest version available from PHPGurukul (check for v1.3 or later)

  1. 1. Check PHPGurukul's official repository or website for the latest version of Online Fire Reporting System
  2. 2. If version 1.3 or later is available, download the latest stable release
  3. 3. Back up the current database and application files before upgrading
  4. 4. Replace the application files with the new version
  5. 5. Verify the /ofrs/admin/edit-team.php endpoint now properly sanitizes the 'teamid' parameter
  6. 6. Test that the edit-team functionality works correctly after the upgrade
  7. 7. Re-scan the application to confirm the SQL injection vulnerability is resolved
Caveat Review release notes for any configuration or database changes required during upgrade

Generated from the published advisory — verify against the referenced sources before acting.

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-40690 — 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-40690 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