Database disclosure via unchecked SQL input
Published Dec 4, 2023 · Updated Jun 3, 2025
SQL injection in SEMCMS 3.9 allows remote attackers to read backend database data by sending crafted application input. Public records do not identify the vulnerable endpoint, parameter, or query; they state only that unchecked input reaches the database interpreter as SQL. No authentication or user interaction is required, and the published impact is limited to unauthorized data disclosure.
Summary
What happened
SQL injection in SEMCMS 3.9 allows remote attackers to read backend database data by sending crafted application input. Public records do not identify the vulnerable endpoint, parameter, or query; they state only that unchecked input reaches the database interpreter as SQL. No authentication or user interaction is required, and the published impact is limited to unauthorized data disclosure.
The record
- CVE
- CVE-2023-48863
- Published
- Dec 4, 2023
- Updated
- Jun 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 4, 2023CVE publishedPublication date reported by the CVE source.
- Jun 3, 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
- NoBlake CVE-2023-48863 exploit repositoryproof 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