Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-11515: SQL Injection in code-projects Online Complaint Site

0
Medium
VulnerabilityCVE-2025-11515cvecve-2025-11515
Published: Thu Oct 09 2025 (10/09/2025, 00:02:08 UTC)
Source: CVE Database V5
Vendor/Project: code-projects
Product: Online Complaint Site

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.

AI-Powered Analysis

AILast updated: 10/09/2025, 00:54:49 UTC

Technical Analysis

CVE-2025-11515 is a SQL injection vulnerability identified in the code-projects Online Complaint Site version 1.0, specifically within the /cms/users/register-complaint.php endpoint. 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 arbitrary SQL commands by manipulating the 'cid' argument, potentially leading to unauthorized data access, modification, or deletion within the backend database. The attack vector is network-based (AV:N), requires low attack complexity (AC:L), no authentication (PR:L indicates low privileges but no authentication needed), and no user interaction (UI:N). The vulnerability impacts confidentiality, integrity, and availability at a limited scope (VC:L, VI:L, VA:L), meaning the attacker can affect some data and system functions but not the entire system. The CVSS 4.0 score of 5.3 reflects a medium severity level. Although no official patches have been released, public exploit code is available, increasing the likelihood of exploitation. The vulnerability is particularly concerning for organizations relying on this software for complaint management, as attackers could extract sensitive user data or disrupt complaint processing services. The lack of authentication requirement and remote exploitability make this a significant risk. The vulnerability was published on October 9, 2025, and no mitigations or patches have been linked yet, emphasizing the need for immediate defensive measures.

Potential Impact

For European organizations using the code-projects Online Complaint Site 1.0, this vulnerability poses a risk of unauthorized access to sensitive complaint data, potentially including personal information of complainants. Exploitation could lead to data breaches, undermining confidentiality and violating data protection regulations such as GDPR. Integrity of complaint records could be compromised, affecting trust in complaint handling processes. Availability may also be impacted if attackers execute destructive SQL commands, causing service disruptions. Public sector entities and private companies managing customer grievances are particularly at risk. The public availability of exploit code increases the threat level, as less skilled attackers can attempt exploitation. The medium severity rating indicates a moderate but tangible risk that could escalate if combined with other vulnerabilities or misconfigurations. Failure to address this vulnerability could result in reputational damage, regulatory penalties, and operational interruptions.

Mitigation Recommendations

1. Immediately implement input validation and sanitization on the 'cid' parameter to ensure only expected data types and values are accepted. 2. Refactor the affected code to use parameterized queries or prepared statements to prevent SQL injection. 3. Conduct a comprehensive code review of all user input handling in the application to identify and remediate similar vulnerabilities. 4. Deploy Web Application Firewalls (WAFs) with rules targeting SQL injection patterns, specifically monitoring requests to /cms/users/register-complaint.php. 5. Monitor database logs for unusual queries or access patterns indicative of injection attempts. 6. Restrict database user permissions to the minimum necessary to limit the impact of potential exploitation. 7. If possible, isolate the complaint management system from other critical infrastructure to contain potential breaches. 8. Engage with the vendor or community to obtain or develop patches and apply them promptly once available. 9. Educate development teams on secure coding practices to prevent recurrence. 10. Prepare incident response plans to quickly address any exploitation attempts.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-10-08T15:13:09.642Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68e7046932de7eb26af0f7c6

Added to database: 10/9/2025, 12:40:09 AM

Last enriched: 10/9/2025, 12:54:49 AM

Last updated: 10/9/2025, 2:49:54 AM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats