CVE-2025-11516VulnerabilityPublished 9 Oct 2025

CVE-2025-11516: 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

To mitigate CVE-2025-11516, organizations should immediately implement input validation and sanitization on the 'cid' parameter to prevent malicious SQL code injection. Employ parameterized queries or prepared statements in the complaint-details.php file to ensure user inputs are safely handled. Restrict database user permissions to the minimum necessary to limit the impact of potential exploitation. Conduct a thorough code review of the entire application to identify and remediate similar injection flaws. If possible, upgrade to a patched version once available or apply vendor-provided fixes. In the interim, consider deploying Web Application Firewalls (WAFs) with rules targeting SQL injection patterns specific to this vulnerability. Monitor logs for unusual database query patterns or access attempts to the vulnerable endpoint. Educate developers on secure coding practices to prevent future injection vulnerabilities. Finally, ensure regular backups of complaint data to enable recovery in case of data corruption or loss.

Description

A weakness has been identified in code-projects Online Complaint Site 1.0. Impacted is an unknown function of the file /cms/users/complaint-details.php. Executing manipulation of the argument cid can lead to sql injection. It is possible to launch the attack remotely. The exploit has been made available to the public and could be exploited.

Impact

For European organizations using the code-projects Online Complaint Site 1.0, this vulnerability poses a significant risk to the confidentiality and integrity of complaint data, which may include personally identifiable information (PII) and sensitive organizational information. Exploitation could lead to unauthorized data disclosure, data tampering, or even deletion, undermining trust in complaint handling processes and potentially violating data protection regulations such as GDPR. The availability impact is limited but possible if attackers manipulate database queries to disrupt service. Public sector entities and private companies relying on this software for customer or citizen complaint management are particularly vulnerable. The medium severity score suggests moderate risk, but the ease of exploitation and public exploit availability increase urgency. Additionally, reputational damage and regulatory penalties could result from data breaches. The vulnerability could be exploited remotely without authentication, broadening the attack surface and increasing the likelihood of attacks targeting European organizations.

Summary

CVE-2025-11516 identifies a SQL injection vulnerability in the code-projects Online Complaint Site version 1.0, specifically within the /cms/users/complaint-details.php file. The vulnerability arises from improper sanitization of the 'cid' parameter, which is used in SQL queries without adequate validation or parameterization. This flaw allows remote attackers to inject malicious SQL code, potentially enabling unauthorized access to or modification of the backend database. The attack vector requires no authentication or user interaction, increasing the risk of exploitation. The CVSS 4.0 base score is 5.3 (medium), reflecting the vulnerability's moderate impact on confidentiality, integrity, and availability, with low complexity and no privileges required. Although no active exploitation in the wild has been reported, the public availability of exploit code raises the risk of imminent attacks. The vulnerability affects only version 1.0 of the product, which is used for managing online complaints, likely storing sensitive user and complaint data. The lack of official patches or mitigation guidance increases exposure. This vulnerability exemplifies common risks in web applications that fail to properly sanitize user inputs, emphasizing the need for secure coding practices such as prepared statements and input validation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Oct 2025, 01:15 UTC

Technical details

References

Community reviews

Related threats