Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Back to vulnerabilities
MediumPublic exploit

SQL Injection in PHPGurukul Online Fire Reporting System 1.2 edit-team.php

IdentifiersCVE-2025-5618CWE-89· Improper Neutralization of Special…

CVE-2025-5618 is a critical SQL injection vulnerability in PHPGurukul Online Fire Reporting System version 1.2. The issue affects the /admin/edit-team.php endpoint, where the teamid argument is not properly sanitized or parameterized before being used in a backend SQL query. An attacker can manipulate this parameter to inject arbitrary SQL syntax, altering the intended database operation. The available content does not identify the exact vulnerable function or query construction routine, but it does specifically attribute the flaw to improper handling of the teamid parameter in that file. The vulnerability is remotely exploitable, and public exploit disclosure indicates that exploitation details are available.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial
ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow an attacker to interfere with application database queries. Depending on the database user privileges and application logic, this may enable unauthorized reading of sensitive data, modification or deletion of records, authentication bypass, and potentially administrative compromise of the application. In severe cases, if the database environment is permissive, it could also facilitate further compromise of the underlying system. The content confirms remote exploitability and public exploit availability, which increases operational risk.

Mitigation

If you can’t patch tonight, do this now.

If an immediate patch is not available, restrict access to the /admin/ interface to trusted networks or administrative VPNs only, and apply strong authentication controls. Deploy a WAF or equivalent filtering to detect and block SQL injection payloads targeting the teamid parameter and other request inputs. Monitor web server, application, and database logs for anomalous requests to /admin/edit-team.php and signs of injection attempts. Reduce database account privileges used by the application to the minimum necessary to limit post-exploitation impact.

Remediation

Patch, then assume compromise.

Upgrade to a fixed version if one is made available by the vendor. In the affected code path, replace dynamic SQL construction involving the teamid parameter with parameterized queries or prepared statements. Enforce strict server-side input validation for teamid, ideally constraining it to the expected type and format, such as an integer. Review /admin/edit-team.php and related administrative handlers for similar unsafe query patterns, and conduct a broader code audit for SQL injection issues across the application.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
PhpgurukulOnline Fire Reporting Systemapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

3 SOURCESView more in app
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Start free trial
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.

EXTERNAL REFERENCES
MITRE CVE
cve.org · CVE-2025-5618
NVD
nvd.nist.gov/vuln/detail/CVE-2025-5618
MITRE CWE · CWE-89
Improper Neutralization of Special Elements…
Third Party Advisory
github.com/YZS17/CVE/blob/main/Online_Fire_Reporting_System/sqli_admin_edit-team.php_teamid.md
Third Party Advisory
vuldb.com/?id.311104
Third Party Advisory
vuldb.com/?submit.589117
Product
phpgurukul.com
Permissions Required
vuldb.com/?ctiid.311104