dbcve.org
Old Age Home Management SystemApplication · Phpgurukul

CVE-2025-2737

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-25
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
A vulnerability was found in PHPGurukul Old Age Home Management System 1.0. It has been classified as critical. This affects an unknown part of the file /admin/contactus.php. The manipulation of the argument pagetitle leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

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 PHPGurukul Old Age Home Management System 1.0 allows remote attackers to inject arbitrary SQL commands via the pagetitle parameter in /admin/contactus.php. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries.

MitigationReplace dynamic SQL queries with parameterized queries (prepared statements) in contactus.php and audit the entire application for similar SQL injection vulnerabilities. Apply input validation and output encoding as defense-in-depth.

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
Old Age Home Management SystemApplication
Affected:= 1.0

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 PHPGurukul Old Age Home Management System is installed
    Locate the application web root directory and identify if this specific application is present. Check for characteristic files such as index.php, admin/index.php, or configuration files that indicate this application.
    Affected if The application directory structure for PHPGurukul Old Age Home Management System is found on the server.
  2. Verify the application version is 1.0
    Check for a version file, README file, or any configuration file within the application that displays the version number. Compare your installed version against the affected range.
    Affected if The installed version is exactly 1.0.
  3. Confirm the vulnerable file exists
    Locate and verify the presence of the file /admin/contactus.php in the web application directory.
    Affected if The file /admin/contactus.php exists in the application.
  4. Check if the admin interface is accessible
    Attempt to access or verify the accessibility of the /admin/ directory and contactus.php through the web server. This may require authentication but the endpoint should be reachable.
    Affected if The /admin/contactus.php endpoint is reachable via HTTP/HTTPS.
  5. Inspect contactus.php for vulnerable SQL construction
    Open contactus.php and search for SQL query patterns that use the pagetitle parameter without parameterized queries. Look for code that directly concatenates the pagetitle parameter into WHERE clauses or other SQL statements.
    Affected if The code contains SQL queries that incorporate the pagetitle parameter without using prepared statements or input sanitization.

A user is affected if they have PHPGurukul Old Age Home Management System version 1.0 installed with the accessible /admin/contactus.php file containing direct SQL query construction with the pagetitle parameter.

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

Replace dynamic SQL queries with parameterized queries (prepared statements) in contactus.php and audit the entire application for similar SQL injection vulnerabilities. Apply input validation and output encoding as defense-in-depth.

Fix this in Old Age Home Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2737 — 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-2737 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