How to fix CVE-2020-36972?

Within 24 hours: Identify all systems running SmartBlog 2.0.1 and isolate from direct internet access; enable Web Application Firewall (WAF) rules to block SQL injection patterns in the 'id_post' parameter. Within 7 days: Implement input validation/parameterized queries at the application layer if possible, or disable the details controller if not business-critical; conduct database access audit. Within 30 days: Upgrade to a patched version (when available) or migrate to an alternative platform; perform forensic review of access logs for exploitation indicators.

Is Smartblog affected by CVE-2020-36972?

SmartBlog 2.0.1 deployments are exposed to a publicly exploitable SQL injection vulnerability that could allow attackers to extract sensitive database information without authentication.

CVE-2020-36972

HIGH

2026-01-28 [email protected]

8.2

CVSS 3.1

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Mar 12, 2026 - 21:54 vuln.today

PoC Detected

Feb 09, 2026 - 17:57 vuln.today

Public exploit code

CVE Published

Jan 28, 2026 - 18:16 nvd

HIGH 8.2

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.

Analysis

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. [CVSS 8.2 HIGH]

Technical Context

Classified as CWE-89 (SQL Injection). Affects Smartblog. 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.

Affected Products

Vendor: Smartdatasoft. Product: Smartblog. Versions: up to 2.0.1.

Remediation

Monitor vendor advisories for a patch. Use parameterized queries. Implement input validation. Restrict network access to the affected service where possible.

Priority Score

Low Medium High Critical

KEV: 0

EPSS: +0.0

CVSS: +41

POC: +20

CVE-2020-36972 vulnerability details – vuln.today

Back

CVE-2020-36972

CVSS Vector

Lifecycle Timeline

Tags

Description

Analysis

Technical Context

Affected Products

Remediation

Priority Score

Share

CVE-2020-36972

CVSS Vector

Lifecycle Timeline

Tags

Description

Analysis

Technical Context

Affected Products

Remediation

Priority Score

Share

External POC / Exploit Code