dbcve.org
Wedding ReservationApplication · Anisha

CVE-2025-7611

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-14
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 code-projects Wedding Reservation 1.0. It has been classified as critical. This affects an unknown part of the file /global.php. The manipulation of the argument lu 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 · moderate confidence

A critical SQL injection vulnerability exists in Wedding Reservation 1.0 in the /global.php file via the 'lu' parameter. This allows remote attackers to inject malicious SQL commands, potentially compromising the entire database and application.

MitigationImplement parameterized queries (prepared statements) for all database operations, especially those using the 'lu' parameter. Apply input validation and use least-privilege 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
Wedding ReservationApplication
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. Identify if Wedding Reservation application is present
    Search the web server document root for files or directories containing 'wedding' or 'reservation' in the name. Look for the main application entry point (commonly index.php) and the /global.php file mentioned in the vulnerability.
    Affected if The Anisha Wedding Reservation application version 1.0 is found on the server.
  2. Confirm the installed version
    Check the application's source files for version information. Look in configuration files, readme files, or the main PHP files for a version string. Compare against the affected version 1.0.
    Affected if The installed version is exactly 1.0.
  3. Locate and inspect the vulnerable file
    Find /global.php in the application directory. Open the file and search for usage of the 'lu' parameter in the code. Look for SQL queries that incorporate this parameter without proper sanitization or prepared statements.
    Affected if The file /global.php exists and contains SQL queries using the 'lu' parameter without parameterized queries.
  4. Check if the application processes user input via 'lu' parameter
    Review the PHP code in global.php to determine if the 'lu' parameter is retrieved from user request (GET/POST) and directly used in database operations. Look for patterns like $_REQUEST['lu'], $_GET['lu'], or $_POST['lu'].
    Affected if The 'lu' parameter is extracted from user input and used directly in SQL queries.
  5. Review web server access logs for exploitation attempts
    Search web server access logs (Apache, Nginx) for requests to the application that include the 'lu' parameter with suspicious patterns such as SQL operators (', OR, UNION, --, etc.) or common SQL injection payloads.

A system is affected if it runs Anisha Wedding Reservation version 1.0 with the /global.php file containing SQL queries that use the 'lu' parameter without prepared 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries (prepared statements) for all database operations, especially those using the 'lu' parameter. Apply input validation and use least-privilege database accounts.

Fix this in Wedding Reservation Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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