dbcve.org
Fighting Cock Information SystemApplication · Code Projects

CVE-2024-0477

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 has been found in code-projects Fighting Cock Information System 1.0 and classified as critical. This vulnerability affects unknown code of the file /admin/action/update-deworm.php. The manipulation of the argument usage_deworm leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-250582 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

SQL injection vulnerability in Fighting Cock Information System 1.0 allows remote attackers to inject malicious SQL code via the usage_deworm parameter in /admin/action/update-deworm.php. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially leading to unauthorized data access, modification, or complete system compromise.

MitigationImplement prepared statements/parameterized queries for all database interactions, particularly for the usage_deworm parameter in update-deworm.php. Apply input validation and output encoding 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. Identify the installed application and version
    Locate the application files and check for version indicators such as a version.php file, README, or any file containing '1.0' as the version number. This may be in the root directory or within documentation files.
    Affected if The application is Fighting Cock Information System version 1.0
  2. Verify the vulnerable file exists
    Check if the file /admin/action/update-deworm.php exists in the web root directory. Navigate to the admin/action subdirectory and confirm the presence of update-deworm.php.
    Affected if The file /admin/action/update-deworm.php exists in the application directory
  3. Inspect the usage_deworm parameter handling
    Open /admin/action/update-deworm.php in a text editor and examine how the usage_deworm parameter is handled. Look for direct insertion of this parameter into SQL queries without using prepared statements or parameterized queries.
    Affected if The code directly uses the usage_deworm POST or GET parameter in an SQL query without sanitization or prepared statements
  4. Check if the application uses a database
    Review the application configuration files (such as config.php, db.php, or similar) to confirm database connectivity. The SQL injection requires an active database connection to be exploitable.
    Affected if The application is configured to use a database and the vulnerable query is executed against it

The environment is affected if Fighting Cock Information System version 1.0 is installed, the file /admin/action/update-deworm.php exists, and the usage_deworm parameter is processed in SQL queries without prepared statements or input sanitization.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement prepared statements/parameterized queries for all database interactions, particularly for the usage_deworm parameter in update-deworm.php. Apply input validation and output encoding as defense-in-depth measures.

Recommended fix Low confidence
  1. 1. Isolate the affected system from the network to prevent remote exploitation of this critical SQL injection vulnerability.
  2. 2. Review the source code of /admin/action/update-deworm.php and locate the line(s) where the usage_deworm parameter is used in SQL queries.
  3. 3. Implement parameterized queries (prepared statements) instead of concatenating user input directly into SQL strings.
  4. 4. For example, if using mysqli, replace direct concatenation with mysqli_prepare() and bind parameters.
  5. 5. Apply input validation and sanitization on the usage_deworm parameter before using it in any database operations.
  6. 6. Apply least-privilege principles to the database user account used by the application - restrict it to only necessary operations.
  7. 7. After remediation, test the update-deworm functionality to ensure the fix works correctly and does not break legitimate usage.
  8. 8. Consider deploying a Web Application Firewall (WAF) as an additional layer of defense while code fixes are being implemented.
Caveat No official upgrade or patch is available for this specific vulnerability in the Fighting Cock Information System. Custom code remediation is required.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fighting Cock Information System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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