CVE-2019-25538: 202CMS v10 beta contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate da

This week

HIGH 8.2REMOTEDOWNGRADE

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

202CMS v10 beta contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the log_user parameter. Attackers can send crafted requests with malicious SQL statements in the log_user field to extract sensitive database information or modify database contents.

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.4% (top 69%)
CISA exploited list	No
Weakness	CWE-89
Published	2026-03-12
Last modified	2026-06-17

Publisher (CNA): VulnCheck · Vendor: konradpl99

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

Am I affected?

Timeline

2026-03-12 16:16 UTCPublished CVE record published
2026-06-17 02:32 UTCUpdated Record last modified

konradpl99 202cms DOWNGRADE

Affected: 10.0 beta

Fixed in: no fixed release known

Safe to downgrade to: a release before 10.0

1. Check installed version

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

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

apt-cache madison 202cms sudo apt install 202cms=<VERSION_BEFORE_10.0> sudo apt-mark hold 202cms

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

dnf --showduplicates list 202cms sudo dnf downgrade 202cms-<VERSION_BEFORE_10.0> sudo dnf versionlock add 202cms

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-2019-25538?

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

Is CVE-2019-25538 being exploited?

CVE-2019-25538 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-2019-25538 affect?

CVE-2019-25538 affects 202cms. Severity is high (CVSS 8.2). 202CMS v10 beta contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the log_user parameter. Attackers can send crafted requests with malicious SQL statem

How urgent is CVE-2019-25538?

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

Related CVEs

CVE-2019-25539 HIGH 8.2 DOWNGRADE 202CMS v10 beta contains a blind SQL injection vulnerability that allows unauthenticated attackers to manipula

References

← Back to latest CVEs