# CVE-2020-36972: SmartBlog 2.0.1 - 'id_post' Blind SQL injection

> Attackers can extract database information via blind SQL injection in the id_post parameter of the SmartBlog plugin.

- **Severity:** High 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jan 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-h5jp-4qg2-hm8r

## What is CVE-2020-36972?

CVE-2020-36972 is a high-severity SQL injection vulnerability in smartdatasoft SmartBlog, published on 28 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2020-36972?

It affects 1 product.


Products: Smartdatasoft Smartblog.

## How do I fix CVE-2020-36972?

No fix has been published for CVE-2020-36972 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-36972 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-36972 exists.

## Other vulnerabilities in smartdatasoft SmartBlog

- [CVE-2021-37538](https://insights.sbomify.com/CVE-2021-37538/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36972 and fix it if it is affected.

What it is: CVE-2020-36972 is a high-severity SQL injection vulnerability in smartdatasoft SmartBlog, published on 28 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-36972 exists.

Affected product: smartdatasoft SmartBlog. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-36972/ (Markdown: https://insights.sbomify.com/CVE-2020-36972/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-36972
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-36972
- OSV: https://osv.dev/vulnerability/CVE-2020-36972

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-36972/
Summaries are generated and may contain mistakes; the official description above is the record.