Cyber Resilience

CVE-2020-36972

HighPublic PoC

Published: 28 January 2026

Published
28 January 2026
Modified
09 February 2026
KEV Added
Patch
CVSS Score v4 8.8 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0028 19.8th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2020-36972 is a high-severity SQL Injection (CWE-89) vulnerability in Smartdatasoft Smartblog. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 19.8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified are NIST 800-53 SI-10 (Information Input Validation) and SI-2 (Flaw Remediation).

Deeper analysis

CVE-2020-36972 is a blind SQL injection vulnerability in SmartBlog 2.0.1, specifically within the 'id_post' parameter of the details controller. This flaw allows attackers to extract database information by injecting crafted SQL queries that systematically test and retrieve contents character by character. It is classified under CWE-89 and carries a CVSS v3.1 base score of 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N).

Unauthenticated remote attackers can exploit this vulnerability over the network with low attack complexity and no user interaction required. Exploitation enables the systematic extraction of sensitive database contents, resulting in high confidentiality impact and low integrity impact, while availability remains unaffected.

Relevant advisories and resources include the SmartBlog GitHub repository at https://github.com/smartdatasoft/smartblog, a proof-of-concept exploit at https://www.exploit-db.com/exploits/48995, and a Vulncheck advisory at https://www.vulncheck.com/advisories/smartblog-idpost-blind-sql-injection.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability details

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…

more

database information.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1213.006 Databases Collection
Adversaries may leverage databases to mine valuable information.
Why these techniques?

Blind SQLi in public-facing web app directly enables remote exploitation (T1190) and systematic DB data extraction (T1213.006).

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2018-25199Shared CWE-89
CVE-2026-27179Shared CWE-89
CVE-2025-0308Shared CWE-89
CVE-2019-25581Shared CWE-89
CVE-2026-27885Shared CWE-89
CVE-2019-25479Shared CWE-89
CVE-2026-1476Shared CWE-89
CVE-2019-25526Shared CWE-89
CVE-2025-69365Shared CWE-89
CVE-2019-25573Shared CWE-89

Affected Assets

smartdatasoft
smartblog
2.0.1

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

prevent

Requires validation of untrusted inputs like the 'id_post' parameter to block crafted SQL queries and prevent blind SQL injection exploitation.

prevent

Directly addresses remediation of the specific flaw in the SmartBlog details controller through timely patching or code correction.

prevent

Enforces restrictions on information inputs at application boundaries to limit the 'id_post' parameter to authorized formats, mitigating SQL injection attempts.

References