CVE-2023-51052: S-CMS v5.0 was discovered to contain a SQL injection vulnerability via the A_formauth parameter at /admin/ajax

This month

CRITICAL 9.8REMOTEDOWNGRADE

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

S-CMS v5.0 was discovered to contain a SQL injection vulnerability via the A_formauth parameter at /admin/ajax.php.

Why this priority

Critical severity
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	0.5% (top 55%)
CISA exploited list	No
Weakness	CWE-89
Published	2023-12-21
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: s-cms

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

Am I affected?

Timeline

2023-12-21 16:15 UTCPublished CVE record published
2026-06-17 06:40 UTCUpdated Record last modified

s-cms s-cms DOWNGRADE

Affected: 5.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 5.0

1. Check installed version

apt-cache policy s-cms || rpm -q s-cms || s-cms --version

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

apt-cache madison s-cms sudo apt install s-cms=<VERSION_BEFORE_5.0> sudo apt-mark hold s-cms

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

dnf --showduplicates list s-cms sudo dnf downgrade s-cms-<VERSION_BEFORE_5.0> sudo dnf versionlock add s-cms

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-2023-51052?

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

Is CVE-2023-51052 being exploited?

CVE-2023-51052 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-2023-51052 affect?

CVE-2023-51052 affects s-cms. Severity is critical (CVSS 9.8). S-CMS v5.0 was discovered to contain a SQL injection vulnerability via the A_formauth parameter at /admin/ajax.php.

How urgent is CVE-2023-51052?

Priority 51/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

PHP vulnerabilities

Related CVEs

CVE-2023-7191 MEDIUM 5.5 DOWNGRADE A vulnerability, which was classified as critical, was found in S-CMS up to 2.0_build20220529-20231006
CVE-2023-7190 MEDIUM 5.5 DOWNGRADE A vulnerability, which was classified as critical, has been found in S-CMS up to 2.0_build20220529-20231006
CVE-2023-7189 MEDIUM 5.5 DOWNGRADE A vulnerability classified as critical was found in S-CMS up to 2.0_build20220529-20231006
CVE-2023-51051 CRITICAL 9.8 DOWNGRADE S-CMS v5.0 was discovered to contain a SQL injection vulnerability via the A_textauth parameter at /admin/ajax
CVE-2023-51050 CRITICAL 9.8 DOWNGRADE S-CMS v5.0 was discovered to contain a SQL injection vulnerability via the A_productauth parameter at /admin/a

References

← Back to latest CVEs