CVE-2020-36972: SmartBlog 2.0.1 contains a blind SQL injection vulnerability in the 'id_post' parameter of the details control

This week

HIGH 8.2REMOTEDOWNGRADE

CVE-2020-36972 is a high-severity flaw (CVSS 8.2) affecting smartblog. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.2 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 73%)
CISA exploited list	No
Weakness	CWE-89
Published	2026-01-28
Last modified	2026-06-17

Publisher (CNA): VulnCheck · Vendor: smartdatasoft

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-01-28 18:16 UTCPublished CVE record published
2026-06-17 03:16 UTCUpdated Record last modified

smartdatasoft smartblog DOWNGRADE

Affected: 2.0.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0.1

1. Check installed version

apt-cache policy smartblog || rpm -q smartblog || smartblog --version

2. No fixed release: DOWNGRADE to a release before 2.0.1 (Debian / Ubuntu)

apt-cache madison smartblog sudo apt install smartblog=<VERSION_BEFORE_2.0.1> sudo apt-mark hold smartblog

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list smartblog sudo dnf downgrade smartblog-<VERSION_BEFORE_2.0.1> sudo dnf versionlock add smartblog

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-36972?

smartblog: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2020-36972 being exploited?

CVE-2020-36972 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-36972 affect?

CVE-2020-36972 affects smartblog. Severity is high (CVSS 8.2). 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 inj

How urgent is CVE-2020-36972?

Priority 45/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs