CVE-2025-11530VulnerabilityPublished 9 Oct 2025

CVE-2025-11530: code-projects Online Complaint Site · SQL Injection

Affects code-projects Online Complaint SiteSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% 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/E:P

Base metrics

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

Threat metrics

Exploit Maturity: POC

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.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Oct 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-25.

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
code-projects Online Complaint Site	Affected =1.0	Fixed in–

AI-suggested

1. Immediately implement strict input validation and sanitization on the 'state' parameter in /cms/admin/state.php to prevent SQL injection. 2. Refactor database queries to use parameterized statements or prepared queries, eliminating direct concatenation of user inputs. 3. Restrict access to the /cms/admin/ directory via network-level controls such as IP whitelisting or VPN access to limit exposure. 4. Monitor web server and database logs for unusual query patterns or error messages indicative of injection attempts. 5. Conduct a comprehensive security audit of the entire application to identify and remediate similar injection flaws. 6. If possible, upgrade to a patched or newer version of the software once available, or consider alternative complaint management solutions with stronger security postures. 7. Educate administrators on the risks of SQL injection and enforce the principle of least privilege on database accounts used by the application. 8. Employ Web Application Firewalls (WAFs) with SQL injection detection rules as an interim protective measure. 9. Regularly back up complaint data and test restoration procedures to mitigate impact of potential data corruption or deletion.

Description

CVE-2025-11530 is a medium-severity SQL injection vulnerability affecting version 1.0 of the code-projects Online Complaint Site, specifically in the /cms/admin/state.php file. The vulnerability arises from improper sanitization of the 'state' parameter, allowing remote attackers to inject malicious SQL commands without authentication or user interaction. Exploitation could lead to partial compromise of confidentiality, integrity, and availability of the backend database. Although no known exploits are currently observed in the wild, the exploit code has been publicly disclosed, increasing the risk of attacks. European organizations using this software for complaint management are at risk of data breaches and service disruption. Mitigation requires immediate input validation, parameterized queries, and restricting access to the vulnerable admin endpoint. Countries with higher adoption of this software or with critical public service complaint platforms are more likely to be targeted. Given the medium CVSS score of 5.

Impact

For European organizations, exploitation of this SQL injection vulnerability could result in unauthorized access to sensitive complaint data, including personal information of complainants, potentially violating GDPR and other privacy regulations. Data integrity could be compromised by unauthorized modification or deletion of complaint records, undermining trust in complaint resolution processes. Availability of the complaint management system could also be affected, disrupting critical public or private sector services. Organizations handling large volumes of citizen or customer complaints are particularly at risk, as data breaches could lead to reputational damage and regulatory penalties. The medium severity suggests moderate but tangible risks, especially if attackers leverage the vulnerability to pivot into broader network compromise. The public availability of exploit code increases the likelihood of opportunistic attacks, making timely mitigation essential to protect European entities.

Summary

CVE-2025-11530 identifies a SQL injection vulnerability in the code-projects Online Complaint Site version 1.0, specifically within the /cms/admin/state.php file. The vulnerability stems from insufficient input validation on the 'state' parameter, which is manipulated to inject arbitrary SQL commands. This flaw allows remote attackers to execute unauthorized SQL queries against the backend database without requiring authentication or user interaction, increasing the attack surface. The vulnerability's CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:L - low privileges), no user interaction (UI:N), and low impact on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). The exploit code has been publicly released, though no active exploitation has been reported yet. The vulnerability can lead to unauthorized data access, modification, or deletion, potentially compromising sensitive complaint data and disrupting complaint management services. The lack of patches or vendor advisories necessitates immediate defensive measures. The vulnerability is significant for organizations relying on this software for complaint handling, especially in public sector or customer service contexts. The attack vector being remote and unauthenticated increases the urgency of mitigation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Oct 2025, 08:56 UTC

Technical details

References

Community reviews

Related threats