dbcve.org
Wedding Reservation Management SystemApplication · Janobe

CVE-2025-11477

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-08
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 security flaw has been discovered in SourceCodester Wedding Reservation Management System 1.0. This vulnerability affects unknown code of the file /global.php. The manipulation of the argument User results in sql injection. The attack may be launched remotely. The exploit has been released to the public and may be exploited.

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 SourceCodester Wedding Reservation Management System 1.0 allows remote attackers to inject malicious SQL queries via the User parameter in /global.php. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially extracting sensitive data, modifying records, or compromising the entire system.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in global.php and all files using the User parameter. Apply input validation and output encoding as defense-in-depth. Consider deploying a WAF as an interim measure.

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
Wedding Reservation 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 Wedding Reservation Management System installation
    Locate the SourceCodester/Janobe Wedding Reservation Management System 1.0 application on your server. Check for the presence of global.php in the web root or application directory.
    Affected if The application is SourceCodester or Janobe Wedding Reservation Management System version 1.0
  2. Locate the vulnerable global.php file
    Navigate to the application directory and identify global.php. This file typically handles database connections and user authentication logic.
    Affected if global.php exists and is part of the application
  3. Inspect the User parameter handling in global.php
    Open global.php and search for SQL queries that incorporate the User parameter directly without using parameterized queries or prepared statements. Look for patterns like 'WHERE User=' followed by unsanitized $_POST or $_GET input.
    Affected if The User parameter is used in dynamic SQL queries without parameterization or input sanitization
  4. Verify user input reaches the vulnerable code path
    Check if the User parameter is received from HTTP requests (via $_POST, $_GET, or similar) and passed directly to the SQL query found in global.php without sanitization functions (such as mysqli_real_escape_string, htmlspecialchars, or parameter binding).
    Affected if User input from HTTP requests flows directly into SQL queries without sanitization or prepared statements

You are affected if you run Wedding Reservation Management System 1.0 and the User parameter in global.php is used in SQL queries without parameterized statements or input sanitization.

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 in global.php and all files using the User parameter. Apply input validation and output encoding as defense-in-depth. Consider deploying a WAF as an interim measure.

Recommended fix Moderate confidence
  1. This is a SourceCodester free PHP application. SourceCodester does not follow traditional security release processes with numbered fixed versions.
  2. There is no documented fixed version, patch, or security update for Wedding Reservation Management System 1.0.
  3. Consider migrating to a maintained wedding management platform with active security support.
  4. If continued use is required, implement strict input validation and parameterized queries on all user-supplied parameters including the User parameter in /global.php.
  5. Deploy the application behind a WAF (Web Application Firewall) as an interim compensating control.
  6. Audit the /global.php file for SQL injection vulnerabilities and refactor to use prepared statements/parameterized queries.
Caveat SourceCodester applications typically do not provide versioned security patches; there is no upgrade path to a fixed release

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

Fix this in Wedding Reservation Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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