Which versions of PHP are affected by CVE-2025-7611?

A publicly disclosed SQL injection vulnerability in Wedding Reservation 1.0 allows remote attackers to compromise database integrity and potentially access sensitive customer information.

Is there a public PoC exploit available for CVE-2025-7611?

Yes, a public proof-of-concept exploit is available for CVE-2025-7611. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2025-7611?

Within 24 hours: Assess whether Wedding Reservation 1.0 is deployed in production and identify all affected systems; implement WAF rules to block malicious 'lu' parameter payloads; disable the vulnerable application if not critical to operations. Within 7 days: Isolate affected systems from production networks if remediation is not feasible; notify stakeholders and legal teams regarding potential data exposure; begin vendor communication for patch availability. Within 30 days: Migrate to a patched version when released; conduct forensic analysis for evidence of exploitation; implement code review practices to prevent similar injection vulnerabilities.

PHP CVE-2025-7611

Q: What is the CVSS score of CVE-2025-7611?

CVE-2025-7611 has a CVSS 4.0 base score of 5.5 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

EUVD-2025-21352 MEDIUM

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') (CWE-74)

2025-07-14 cna@vuldb.com

PHP SQLi Wedding Reservation Anisha

5.5

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

5.5 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Severity Changed

Apr 29, 2026 - 01:11 NVD

HIGH MEDIUM

CVSS changed

Apr 29, 2026 - 01:11 NVD

7.3 (HIGH) 5.5 (MEDIUM)

EUVD ID Assigned

Mar 16, 2026 - 09:43 euvd

EUVD-2025-21352

Analysis Generated

Mar 16, 2026 - 09:43 vuln.today

PoC Detected

Jul 15, 2025 - 18:08 vuln.today

Public exploit code

CVE Published

Jul 14, 2025 - 15:15 nvd

HIGH 7.3

DescriptionCVE.org

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.

AnalysisAI

CVE-2025-7611 is a critical SQL injection vulnerability in code-projects Wedding Reservation version 1.0, affecting the /global.php file's 'lu' parameter. Remote unauthenticated attackers can exploit this to execute arbitrary SQL queries, potentially leading to unauthorized data access, modification, or deletion. The vulnerability has been publicly disclosed with exploit code available, significantly increasing real-world exploitation risk.

Technical ContextAI

This vulnerability stems from CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), which manifests as SQL injection through insufficient input validation/sanitization. The /global.php file in Wedding Reservation 1.0 fails to properly escape or parameterize the 'lu' parameter before incorporating it into SQL queries. The attack vector is network-based with no authentication required (PR:N) and low attack complexity (AC:L), meaning standard SQL injection techniques (UNION-based, time-based blind, or error-based) are likely viable. The affected product is code-projects Wedding Reservation version 1.0, a web-based reservation management application written in PHP.

RemediationAI

Immediate actions: (1) Identify all instances of Wedding Reservation 1.0 in production and take offline if possible or restrict network access; (2) Apply vendor patches if available (check code-projects repository or official advisories for patched versions); (3) If patches unavailable, implement Web Application Firewall (WAF) rules to block SQL injection payloads in the 'lu' parameter (common patterns: UNION, SELECT, OR 1=1, SLEEP(), BENCHMARK()); (4) Force parameterized queries/prepared statements in /global.php for all database interactions; (5) Conduct emergency code review of global.php and similar entry points; (6) Implement input validation (whitelist allowed characters for 'lu') and output encoding; (7) Monitor database logs for suspicious queries. Long-term: upgrade to a maintained reservation system or require immediate vendor security updates before continued use.