dbcve.org
Curfew E Pass Management SystemApplication · Phpgurukul

CVE-2025-5562

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-04
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
Public exploit 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 Curfew e-Pass Management System 1.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file /admin/edit-category-detail.php. The manipulation of the argument editid leads to sql injection. The attack may be launched 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 Curfew e-Pass Management System 1.0 allows remote attackers to inject malicious SQL commands via the 'editid' parameter in /admin/edit-category-detail.php. The application fails to properly sanitize user input before using it in database queries.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements to neutralize SQL injection vectors. Validate and sanitize all user inputs, and apply principle of least privilege to 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
Curfew E Pass 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 Curfew e-Pass Management System is installed
    Search for files or directories containing 'curfew' or 'epass' in your web server document root (e.g., /var/www/html, /htdocs, C:\inetpub\wwwroot). Look for the application installation directory.
    Affected if The application is not present in your environment.
  2. Verify the installed version is 1.0
    Check for a version file, README, or any file containing version information within the application directory. Look in files like version.php, README.txt, or the main index.php for a version string.
    Affected if The installed version is not 1.0 (the vulnerability only affects version 1.0).
  3. Locate the vulnerable script
    Check if the file /admin/edit-category-detail.php exists within your installation. Navigate to your application directory and search for this specific file path.
    Affected if The file /admin/edit-category-detail.php does not exist in your installation.
  4. Inspect the editid parameter handling
    Open /admin/edit-category-detail.php in a text editor and examine how the 'editid' parameter is processed. Look for SQL queries that directly incorporate the editid parameter without using prepared statements, parameter binding, or proper escaping.
    Affected if The code directly uses the editid parameter in SQL queries without parameterized queries or input sanitization.
  5. Test for SQL injection vulnerability (if authorized)
    If you have authorization, send a crafted request to /admin/edit-category-detail.php with editid=1' (including a single quote) and observe if a SQL syntax error is returned, or use automated SQL injection testing tools in an authorized security assessment.
    Affected if The application returns SQL errors or behaves unexpectedly when special characters are provided in the editid parameter.

Your environment is affected if you have PHPGurukul Curfew e-Pass Management System version 1.0 installed with the /admin/edit-category-detail.php file present and the editid parameter processed without parameterized queries.

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 to neutralize SQL injection vectors. Validate and sanitize all user inputs, and apply principle of least privilege to database accounts.

Fix this in Curfew E Pass Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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