Gate Pass Management SystemApplication · Projectworlds

CVE-2025-11557

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-09
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 has been found in projectworlds Gate Pass Management System 1.0. This issue affects some unknown processing of the file /add-pass.php. Such manipulation of the argument fullname leads to sql injection. The attack can be executed 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 · moderate confidence

A critical SQL injection vulnerability exists in projectworlds Gate Pass Management System 1.0. The vulnerability is located in the fullname parameter of /add-pass.php, where user input is not properly sanitized before being used in database queries. An unauthenticated remote attacker can exploit this to inject arbitrary SQL commands, potentially gaining full database access or compromising the application.

MitigationImmediate remediation requires updating the /add-pass.php file to use parameterized queries (prepared statements) instead of directly embedding user input in SQL strings. Input validation and escaping should also be implemented as defense-in-depth. The publicly available exploit means urgent patching is critical.

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
Gate 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. Locate the vulnerable PHP file
    Search the web server document root for the file /add-pass.php or add-pass.php in the gate pass management system installation directory.
    Affected if The file add-pass.php exists in the application directory structure.
  2. Confirm the application version
    Check the application's main index file, README, or any version file for the exact version number. Compare against the affected version: 1.0.
    Affected if The installed version is Projectworlds Gate Pass Management System 1.0.
  3. Inspect the fullname parameter handling in add-pass.php
    Open add-pass.php and search for the SQL query that handles the 'fullname' parameter. Look for direct string concatenation or interpolation of $_POST['fullname'] or $_REQUEST['fullname'] into the SQL query without using prepared statements or parameter binding.
    Affected if The code shows direct insertion of the fullname parameter into a SQL query (e.g., $sql = "INSERT INTO... '$fullname'...") rather than using prepared statements with placeholders.
  4. Verify database interaction uses direct queries
    Review add-pass.php to see if mysqli_query, mysql_query, PDO::query, or similar functions are called with SQL strings built using user input, rather than using parameterized queries.
    Affected if Database queries are constructed by concatenating user input directly into SQL strings.

If the application is version 1.0 and add-pass.php contains SQL queries that directly embed the fullname parameter without prepared statements, 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

Immediate remediation requires updating the /add-pass.php file to use parameterized queries (prepared statements) instead of directly embedding user input in SQL strings. Input validation and escaping should also be implemented as defense-in-depth. The publicly available exploit means urgent patching is critical.

Fix this in Gate Pass Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-11557 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