Sensitive-data disclosure via edit_breed.php SQL injection
Published May 31, 2023 · Updated Jan 10, 2025
SQL injection in Fighting Cock Information System 1.0 allows remote attackers to read sensitive data through edit_breed.php. Public sources identify edit_breed.php as the injection locus but do not disclose the affected parameter or SQL construction. No authentication or user interaction is required, and the published impact is limited to database confidentiality.
Summary
What happened
SQL injection in Fighting Cock Information System 1.0 allows remote attackers to read sensitive data through edit_breed.php. Public sources identify edit_breed.php as the injection locus but do not disclose the affected parameter or SQL construction. No authentication or user interaction is required, and the published impact is limited to database confidentiality.
The record
- CVE
- CVE-2021-31233
- Published
- May 31, 2023
- Updated
- Jan 10, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 31, 2023CVE publishedPublication date reported by the CVE source.
- Jan 10, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo