Unauthenticated database disclosure via single.php id injection
Published May 4, 2022 · Updated Aug 3, 2024
SQL injection in Sourcecodester Fantastic Blog CMS 1.0 allows remote attackers to extract database metadata via the id parameter in single.php. The endpoint incorporates the id value into a database query without neutralizing attacker-controlled SQL syntax, enabling a UNION SELECT payload. No authentication or user interaction is required; the published proof of concept extracts the database name and database-user value.
Summary
What happened
SQL injection in Sourcecodester Fantastic Blog CMS 1.0 allows remote attackers to extract database metadata via the id parameter in single.php. The endpoint incorporates the id value into a database query without neutralizing attacker-controlled SQL syntax, enabling a UNION SELECT payload. No authentication or user interaction is required; the published proof of concept extracts the database name and database-user value.
The record
- CVE
- CVE-2022-28512
- Published
- May 4, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 4, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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
- Fantastic Blog CMS single.php SQL injection proof of conceptproof of concept · unverified
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