CVE-2025-5566VulnerabilityPublished 4 Jun 2025

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

Affects PHPGurukul Notice Board SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Packagistphpgurukul/notice-board-system`pkg:composer/phpgurukul/notice-board-system`Other threats	Affected =1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Since no official patches are currently available, European organizations should implement the following specific mitigations: 1) Immediately audit and restrict database user permissions to the minimum necessary, ensuring the web application user has no more than read-only access where possible. 2) Implement Web Application Firewall (WAF) rules to detect and block SQL injection patterns targeting the 'searchdata' parameter in /search-notice.php. 3) Conduct a thorough code review and apply input validation and parameterized queries or prepared statements to sanitize 'searchdata' inputs, if source code access is available. 4) Monitor web server and database logs for unusual query patterns or spikes in errors related to search functionality. 5) Consider temporarily disabling or restricting access to the search feature until a patch or secure update is released. 6) Engage with the vendor or community to obtain or develop patches and apply them promptly once available. 7) Educate administrators about the risks and signs of exploitation to enable rapid incident response. These targeted actions go beyond generic advice by focusing on immediate risk reduction and detection tailored to this specific vulnerability and application context.

Description

A vulnerability classified as critical has been found in PHPGurukul Notice Board System 1.0. This affects an unknown part of the file /search-notice.php. The manipulation of the argument searchdata leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations, the impact of this vulnerability depends on the extent of PHPGurukul Notice Board System deployment. Institutions such as universities, schools, or small enterprises using this system could face data breaches exposing sensitive internal communications or personal data. This could lead to reputational damage, regulatory fines under GDPR for data leakage, and operational disruption if the database integrity is compromised. Since the vulnerability allows remote exploitation without authentication, attackers could automate attacks at scale, increasing the risk of widespread data exposure. Additionally, if the database contains personally identifiable information (PII) or confidential organizational data, the breach could have legal and financial consequences. The medium severity rating suggests that while the impact is not catastrophic, it is significant enough to warrant immediate attention. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate it, especially given the public disclosure. European organizations must consider the potential for targeted attacks exploiting this vulnerability, particularly in sectors with high data sensitivity such as education, healthcare, and government.

Summary

CVE-2025-5566 is a SQL Injection vulnerability identified in version 1.0 of the PHPGurukul Notice Board System, specifically within the /search-notice.php file. The vulnerability arises from improper sanitization or validation of the 'searchdata' parameter, which is directly used in SQL queries. This flaw allows an unauthenticated remote attacker to inject malicious SQL code into the backend database query. Exploiting this vulnerability could enable attackers to manipulate database queries, potentially leading to unauthorized data disclosure, data modification, or even deletion. The vulnerability is remotely exploitable without user interaction or authentication, increasing its risk profile. However, the CVSS 4.0 score is 5.3 (medium severity), reflecting limited impact on confidentiality, integrity, and availability, and the requirement of low privileges (PR:L) but no user interaction or authentication. The vulnerability does not have known exploits in the wild yet, and no official patches or mitigations have been published at the time of disclosure. The lack of a patch increases the urgency for affected organizations to implement compensating controls. The vulnerability's vector metrics indicate network attack vector (AV:N), low attack complexity (AC:L), no privileges required (AT:N), no user interaction (UI:N), and low impact on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). This suggests that while the vulnerability is exploitable remotely and easily, the potential damage is somewhat limited, possibly due to the application's design or database permissions. Given the nature of SQL injection, attackers could extract sensitive information, bypass authentication, or corrupt data if the backend database permissions are not properly restricted. The PHPGurukul Notice Board System is a web-based application used for posting and managing notices, likely deployed in educational institutions, small businesses, or community organizations. The vulnerability's exploitation could lead to leakage of sensitive notices or user data, undermining trust and compliance with data protection regulations.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Jul 2025, 00:11 UTC

Technical details

References

Community reviews

Related threats