Database disclosure via injectable id_post predicate
Published Jan 28, 2026 · Updated Jan 28, 2026
Blind SQL injection in SmartDataSoft SmartBlog 2.0.1 allows remote attackers to read database contents through the details controller. The controller evaluates SQL expressions supplied through id_post, exposing a page-length oracle for injected Boolean substring tests. No authentication or user interaction is required, and repeated requests disclose selected database values character by character.
Summary
What happened
Blind SQL injection in SmartDataSoft SmartBlog 2.0.1 allows remote attackers to read database contents through the details controller. The controller evaluates SQL expressions supplied through id_post, exposing a page-length oracle for injected Boolean substring tests. No authentication or user interaction is required, and repeated requests disclose selected database values character by character.
The record
- CVE
- CVE-2020-36972
- Published
- Jan 28, 2026
- Updated
- Jan 28, 2026
- Vendor
- SmartDataSoft
- Product
- SmartBlog
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 28, 2026CVE publishedPublication date reported by the CVE source.
- Jan 28, 2026Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.1
What conditions does exploitation require?
What is affected?
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
- SmartBlog 2.0.1 id_post blind SQL injection exploitfunctional · validated
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