What is the CVSS score of CVE-2025-5639?

CVE-2025-5639 has a CVSS 3.1 base score of 7.3 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L. EPSS exploitation probability: 0.1%.

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

A critical SQL injection vulnerability in PHPGurukul Notice Board System 1.0 allows remote attackers to compromise database integrity and potentially access sensitive user data through the password…

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

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

How to fix or mitigate CVE-2025-5639?

Within 24 hours: Immediately disable or restrict access to the /forgot-password.php endpoint using firewall or WAF rules; audit access logs for exploitation attempts. Within 7 days: Conduct a full vulnerability assessment of all deployed instances and determine if alternative notice board solutions are available for migration. Within 30 days: Either migrate to a patched version when available, replace the application with a maintained alternative, or implement comprehensive input validation and parameterized queries through code review and remediation if in-house development is feasible.

PHP CVE-2025-5639

EUVD-2025-16969 HIGH

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

2025-06-05 cna@vuldb.com

PHP SQLi Notice Board System Phpgurukul

7.3

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.3 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

Low

Lifecycle Timeline

EUVD ID Assigned

Mar 14, 2026 - 17:53 euvd

EUVD-2025-16969

Analysis Generated

Mar 14, 2026 - 17:53 vuln.today

PoC Detected

Jun 06, 2025 - 20:12 vuln.today

Public exploit code

CVE Published

Jun 05, 2025 - 06:15 nvd

HIGH 7.3

DescriptionCVE.org

A vulnerability was found in PHPGurukul Notice Board System 1.0 and classified as critical. Affected by this issue is some unknown functionality of the file /forgot-password.php. The manipulation of the argument email leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

AnalysisAI

Critical SQL injection vulnerability in PHPGurukul Notice Board System 1.0 affecting the /forgot-password.php endpoint via the email parameter. An unauthenticated remote attacker can exploit this with low complexity to execute arbitrary SQL queries, potentially compromising confidentiality, integrity, and availability of the underlying database. The vulnerability has been publicly disclosed with exploit code available, increasing real-world exploitation risk.

Technical ContextAI

This vulnerability exploits improper input validation in the password recovery functionality of PHPGurukul Notice Board System. The root cause is classified under CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component - 'Injection'), which encompasses SQL injection attacks. The /forgot-password.php file fails to properly sanitize or parameterize the email parameter before incorporating it into SQL queries, allowing an attacker to inject malicious SQL syntax. PHPGurukul is a PHP-based notice board application commonly deployed on shared hosting environments. The vulnerability likely resides in a query similar to: SELECT * FROM users WHERE email = '[USER_INPUT]' or UPDATE statements that reconstruct user credentials without prepared statements or input validation.

RemediationAI

Immediate actions: (1) Patch to a fixed version if available from PHPGurukul developers - verify official repository (github.com/phpgurukul if maintained); (2) If no patch exists, implement input validation on the email parameter using regex whitelist (^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$); (3) Replace all dynamic SQL with parameterized queries/prepared statements using mysqli prepared statements or PDO with bound parameters; (4) Apply Web Application Firewall (WAF) rules to block common SQL injection patterns in POST/GET email parameters; (5) Disable or restrict access to /forgot-password.php if not actively used; (6) Implement database user permissions principle of least privilege (read-only for password reset queries); (7) Enable SQL error suppression in production to prevent information disclosure. Vendor advisory: Check PHPGurukul GitHub releases and security advisories for official patches.