Skip to main content
VulnerabilityPublished

CVE-2025-5639: PHPGurukul Notice Board System · SQL Injection

Affects PHPGurukul Notice Board SystemSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
PHPGurukul Notice Board SystemAffected
  • =1.0
Fixed in–

AI-suggested

  1. Immediate mitigation should include implementing web application firewall (WAF) rules to detect and block SQL injection patterns targeting the /forgot-password.php endpoint, especially filtering suspicious 'email' parameter inputs.
  2. Organizations should audit their PHPGurukul Notice Board System installations to confirm the version in use; if version 1.0 is deployed, consider disabling the forgot-password functionality temporarily until a patch is available.
  3. Employ input validation and parameterized queries or prepared statements in the application code to prevent SQL injection; if source code access is available, developers should remediate the vulnerable code promptly.
  4. Monitor logs for unusual database query patterns or repeated failed password reset attempts that could indicate exploitation attempts.
  5. Restrict database user permissions to the minimum necessary to limit the impact of a successful injection.
  6. If feasible, isolate the affected system within the network and limit external access to reduce exposure.
  7. Stay updated with vendor advisories for patches or official fixes and apply them immediately once released.

Description

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.

References

Community reviews

Loading reviews…