CVE-2018-17391: SQL Injection exists in authors_post.php in Super Cms Blog Pro 1.0 via the author parameter.

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2018-17391 is a critical-severity flaw (CVSS 9.8) affecting super cms blog pro. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

SQL Injection exists in authors_post.php in Super Cms Blog Pro 1.0 via the author parameter.

Why this priority

Critical 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	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	3.2% (top 12%)
CISA exploited list	No
Weakness	CWE-89
Published	2018-09-28
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: super cms blog pro project

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

Am I affected?

Timeline

2018-09-28 00:29 UTCPublished CVE record published
2026-06-17 01:45 UTCUpdated Record last modified

super cms blog pro project super cms blog pro DOWNGRADE

Affected: 1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0

1. Check installed version

apt-cache policy super-cms-blog-pro || rpm -q super-cms-blog-pro || super-cms-blog-pro --version

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

apt-cache madison super-cms-blog-pro sudo apt install super-cms-blog-pro=<VERSION_BEFORE_1.0> sudo apt-mark hold super-cms-blog-pro

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

dnf --showduplicates list super-cms-blog-pro sudo dnf downgrade super-cms-blog-pro-<VERSION_BEFORE_1.0> sudo dnf versionlock add super-cms-blog-pro

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.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: Super Cms Blog Pro 1.0 - SQL Injection

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-2018-17391?

super cms blog pro: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2018-17391 being exploited?

CVE-2018-17391 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-2018-17391 affect?

CVE-2018-17391 affects super cms blog pro. Severity is critical (CVSS 9.8). SQL Injection exists in authors_post.php in Super Cms Blog Pro 1.0 via the author parameter.

How urgent is CVE-2018-17391?

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

Software pages

PHP vulnerabilities

References

← Back to latest CVEs