dbcve.org
Chat SystemApplication · Code Projects

CVE-2024-13035

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been found in code-projects Chat System 1.0 and classified as critical. This vulnerability affects unknown code of the file /admin/update_user.php. The manipulation of the argument id leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in the id parameter of /admin/update_user.php in code-projects Chat System 1.0 allows remote attackers to execute arbitrary SQL commands via unsanitized user input, potentially leading to unauthorized database access, data exfiltration, or privilege escalation.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in update_user.php and implement proper input validation on the id parameter. Conduct a broader code review to identify and remediate similar SQL injection vulnerabilities throughout the application.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Chat SystemApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Chat System installation directory
    Search the web server document root for files containing 'chat', 'chat system', or similar naming patterns. Common paths may include /var/www/html/, /htdocs/, or C:\inetpub\wwwroot\. Look for directories containing 'code-projects' or 'chat-system'.
    Affected if The Code Projects Chat System application is present on the server.
  2. Confirm the installed version is 1.0
    Check for a version file, README, or any file containing 'version' or '1.0' within the Chat System directory. Alternatively, inspect the main index.php or config files for a version declaration.
    Affected if The installed version is exactly 1.0.
  3. Verify the vulnerable file exists
    Locate the file /admin/update_user.php within the Chat System installation directory. Check if this file is present on the filesystem.
    Affected if The file /admin/update_user.php exists in the application.
  4. Determine if the admin panel is accessible
    Check if the /admin/ directory or update_user.php is reachable from the network. Attempt to access the URL path externally or verify through web server configuration that the endpoint responds to HTTP requests.
    Affected if The /admin/update_user.php endpoint is accessible via HTTP/HTTPS.
  5. Inspect the id parameter handling in update_user.php
    Open /admin/update_user.php in a text editor or use 'grep' to search for SQL query patterns. Look for direct use of $_GET['id'] or $_POST['id'] in SQL statements without prepared statements, parameter binding, or input sanitization functions such as mysqli_prepare, PDO::prepare, or htmlspecialchars.
    Affected if The code contains unsanitized SQL queries using the 'id' parameter without prepared statements or parameter binding.

A user is affected if they have Code Projects Chat System version 1.0 installed with the accessible /admin/update_user.php file containing unsanitized SQL queries on the id parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements in update_user.php and implement proper input validation on the id parameter. Conduct a broader code review to identify and remediate similar SQL injection vulnerabilities throughout the application.

Fix this in Chat System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13035 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-13035 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data