CVE-2022-38923: BluePage CMS thru v3.9 processes an insufficiently sanitized HTTP Header allowing MySQL Injection in the 'User

Q: How do I fix CVE-2022-38923?

bluepage cms: upgrade to newer than 3.9. Exact commands for each OS are on this page.

Q: Is CVE-2022-38923 being exploited?

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

Q: What does CVE-2022-38923 affect?

CVE-2022-38923 affects bluepage cms. Severity is critical (CVSS 9.8). BluePage CMS thru v3.9 processes an insufficiently sanitized HTTP Header allowing MySQL Injection in the 'User-Agent' field using a Time-based blind SLEEP payload.

Q: How urgent is CVE-2022-38923?

Priority 65/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

This week

CRITICAL 9.8REMOTEWATCHLISTUPGRADE

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

BluePage CMS thru v3.9 processes an insufficiently sanitized HTTP Header allowing MySQL Injection in the 'User-Agent' field using a Time-based blind SLEEP payload.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.0% (top 36%)
CISA exploited list	No
Weakness	CWE-89
Published	2023-04-03
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: iss-oberlausitz

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

Am I affected?

Timeline

2023-04-03 15:15 UTCPublished CVE record published
2026-06-17 04:57 UTCUpdated Record last modified

iss-oberlausitz bluepage cms UPGRADE

Affected: <= 3.9

Fixed in: newer than 3.9

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to newer than 3.9 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade bluepage-cms

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade bluepage-cms

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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-2022-38923?

bluepage cms: upgrade to newer than 3.9. Exact commands for each OS are on this page.

Is CVE-2022-38923 being exploited?

CVE-2022-38923 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-2022-38923 affect?

CVE-2022-38923 affects bluepage cms. Severity is critical (CVSS 9.8). BluePage CMS thru v3.9 processes an insufficiently sanitized HTTP Header allowing MySQL Injection in the 'User-Agent' field using a Time-based blind SLEEP payload.

How urgent is CVE-2022-38923?

Priority 65/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

Software pages

MySQL vulnerabilities

Related CVEs

CVE-2022-38922 CRITICAL 9.8 UPGRADE BluePage CMS thru 3.9 processes an insufficiently sanitized HTTP Header Cookie value allowing MySQL Injection

References

← Back to latest CVEs