CVE-2020-36972 Details
Description
SmartBlog 2.0.1 contains a blind SQL injection vulnerability in the 'id_post' parameter of the details controller that allows attackers to extract database information. Attackers can systematically test and retrieve database contents by injecting crafted SQL queries that compare character-by-character of database information.
A blind SQL injection vulnerability has been identified in SmartBlog version 2.0.1. The issue resides in the 'id_post' parameter of the details controller, allowing attackers to extract database information. Exploitation involves injecting crafted SQL queries that compare database information character by character, enabling systematic retrieval of data.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jan 28, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://www.exploit-db.com/exploits/48995 | CISA-ADP | Exploit |
| https://github.com/smartdatasoft/smartblog | [email protected] | Product |
| https://www.exploit-db.com/exploits/48995 | [email protected] | Exploit |
| https://www.vulncheck.com/advisories/smartblog-idpost-blind-sql-injection | [email protected] | Third Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-89 | Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| smartdatasoft smartblog | 2.0.1 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Feb 9, 2026 | Initial Analysis | [email protected] |
| Jan 28, 2026 | CVE Modified | CISA-ADP |
| Jan 28, 2026 | New CVE Received | [email protected] |