CVE-2025-11479
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 · uneditedA security vulnerability has been detected in SourceCodester Wedding Reservation Management System 1.0. Impacted is the function insertReservation of the file function.php. Such manipulation of the argument number leads to sql injection. The attack can be executed remotely. The exploit has been disclosed publicly 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 confidenceA critical SQL injection vulnerability exists in the insertReservation function of function.php in SourceCodester Wedding Reservation Management System 1.0. The 'number' parameter is not properly sanitized, allowing remote attackers to inject arbitrary SQL queries. This can lead to unauthorized database access, data exfiltration, or potential system compromise.
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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the Wedding Reservation Management System versionLocate the application source files and check for version indicators such as a version file, README, or header comments in main PHP files. The affected version is 1.0.Affected if The installed version is 1.0 of the Wedding Reservation Management System.
-
Locate function.php in the applicationSearch the web root directory for function.php. This file typically resides in the includes or functions subdirectory of the application.Affected if function.php exists in the application structure.
-
Identify the insertReservation functionOpen function.php and search for the insertReservation function definition. This function handles reservation data submission.Affected if The insertReservation function exists in function.php.
-
Examine the 'number' parameter handlingWithin the insertReservation function, locate where the 'number' parameter is processed. Look for SQL query construction that incorporates this parameter directly without sanitization.Affected if The 'number' parameter is used in a SQL query without prepared statements, parameter binding, or input sanitization functions.
-
Verify the vulnerability is exploitableCheck if the insertReservation function is accessible via an HTTP request (such as through an AJAX call or form submission). Review if user input for the 'number' parameter reaches the vulnerable SQL query.Affected if The insertReservation function can be invoked and the 'number' parameter is passed directly to a SQL query without protection.
You are affected if you run Wedding Reservation Management System version 1.0 and the 'number' parameter in function.php's insertReservation function is processed in SQL queries without prepared statements or sanitization.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements in the insertReservation function and audit all other user inputs for similar vulnerabilities. Apply input validation and least-privilege database accounts as defense-in-depth measures.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11479 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11479 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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