dbcve.org
Fighting Cock Information SystemApplication · Code Projects

CVE-2024-0485

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-13
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, which was classified as critical, was found in code-projects Fighting Cock Information System 1.0. Affected is an unknown function of the file admin/pages/tables/add_con.php. The manipulation of the argument id leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-250590 is the identifier assigned to this vulnerability.

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

A critical SQL injection vulnerability exists in Fighting Cock Information System 1.0 within the admin/pages/tables/add_con.php file. The 'id' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL commands.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in add_con.php. Implement input validation and least-privilege database accounts as defense-in-depth measures.

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
Fighting Cock Information 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. Confirm Fighting Cock Information System 1.0 is installed
    Search for the application directory or check web server document roots for folders containing 'fighting cock' or 'cock' in the name, or look for the specific file path admin/pages/tables/add_con.php
    Affected if The application directory or the file admin/pages/tables/add_con.php exists on the system
  2. Locate and inspect add_con.php
    Navigate to admin/pages/tables/add_con.php in the application directory and open the file to examine the code
    Affected if The file exists and contains SQL query logic that uses the 'id' parameter
  3. Check if the id parameter is used in dynamic SQL
    Search within add_con.php for SQL query patterns (SELECT, INSERT, UPDATE, DELETE) that concatenate or embed the 'id' parameter directly without using prepared statements or parameter binding
    Affected if The code constructs SQL queries by directly inserting the 'id' parameter into the query string without sanitization or parameterization
  4. Verify admin interface is accessible
    Check if the admin/pages/ directory is accessible via the web server and whether authentication is required or if the endpoint is exposed
    Affected if The add_con.php file can be accessed remotely without authentication or with compromised admin credentials
  5. Test for SQL injection presence
    If accessible, send a request to add_con.php with SQL injection payloads in the 'id' parameter (e.g., id=1' OR '1'='1) and observe database responses or errors
    Affected if The application returns database errors or exhibits unexpected behavior based on injected SQL syntax

You are affected if Fighting Cock Information System 1.0 is installed with the admin/pages/tables/add_con.php file present and the code contains unsanitized 'id' parameter usage in dynamic SQL queries that can be accessed remotely.

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 add_con.php. Implement input validation and least-privilege database accounts as defense-in-depth measures.

Fix this in Fighting Cock Information System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0485 — 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-0485 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