CVE-2025-11515VulnerabilityPublished 9 Oct 2025

CVE-2025-11515: 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-11515, organizations should immediately implement input validation and sanitization for the 'cid' parameter in the /cms/users/register-complaint.php script. Employ parameterized queries or prepared statements to prevent SQL injection. Conduct a thorough code review of all input handling in the application to identify and remediate similar vulnerabilities. Restrict database user permissions to the minimum necessary to limit potential damage from exploitation. Monitor logs for suspicious SQL activity or unusual access patterns. If possible, isolate the affected system from critical networks until patched. Apply web application firewalls (WAFs) with rules to detect and block SQL injection attempts targeting this parameter. Educate developers on secure coding practices to prevent recurrence. Regularly update and patch the software once a vendor fix is released.

Description

A security flaw has been discovered in code-projects Online Complaint Site 1.0. This issue affects some unknown processing of the file /cms/users/register-complaint.php. Performing manipulation of the argument cid results in sql injection. It is possible to initiate the attack remotely. The exploit has been released to the public and may be exploited.

Impact

For European organizations, especially those in public administration, customer service, or complaint management sectors using the affected Online Complaint Site software, this vulnerability poses a significant risk. Exploitation could lead to unauthorized disclosure of sensitive personal data, violating GDPR and other data protection regulations, resulting in legal and financial penalties. Integrity of complaint records could be compromised, undermining trust and operational effectiveness. Availability could also be affected if attackers execute destructive SQL commands or cause database corruption. The medium severity rating reflects moderate impact potential, but the public availability of exploit code increases the likelihood of attacks. Organizations with limited security controls or outdated software are particularly vulnerable. The breach of confidentiality and integrity could have reputational damage and operational disruption, especially for government agencies or consumer-facing services in Europe.

Summary

CVE-2025-11515 identifies a SQL injection vulnerability in the code-projects Online Complaint Site version 1.0, specifically within the /cms/users/register-complaint.php script. The vulnerability arises from improper sanitization of the 'cid' parameter, which is used in SQL queries without adequate validation or parameterization. This allows remote attackers to inject malicious SQL code by manipulating the 'cid' argument, potentially leading to unauthorized access to the backend database. The attack vector is network-based (AV:N), requires low attack complexity (AC:L), no privileges (PR:L) but some limited privileges are needed, and no user interaction (UI:N). The vulnerability affects the confidentiality, integrity, and availability of the system but with limited scope and impact (VC:L, VI:L, VA:L). The exploit has been publicly disclosed, increasing the risk of exploitation, although no active exploitation has been reported yet. The vulnerability does not require authentication or user interaction, making it more accessible to attackers. The lack of a patch or official fix at the time of publication increases exposure. This vulnerability is typical of SQL injection flaws where input parameters are not properly sanitized, allowing attackers to execute arbitrary SQL commands, potentially extracting sensitive data, modifying records, or disrupting service availability.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats