CVE-2023-38000: Auth

Q: How do I fix CVE-2023-38000?

wordpress: upgrade to newer than 6.3.1; gutenberg: upgrade to newer than 16.8.0. Exact commands for each OS are on this page.

Q: Is CVE-2023-38000 being exploited?

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

CVE-2023-38000 affects wordpress, gutenberg. Severity is medium (CVSS 6.5). Auth. Stored (contributor+) Cross-Site Scripting (XSS) vulnerability in WordPress core 6.3 through 6.3.1, from 6.2 through 6.2.2, from 6.1 through 6.1.3, from 6.0 through 6.0.5, from 5.9 through 5.9.7 and Gutenberg plugin <= 16.8.0 versions

Q: How urgent is CVE-2023-38000?

Priority 42/100. Public exploit reference

This month

MEDIUM 6.5UPGRADEUPGRADE

CVE-2023-38000 is a medium-severity flaw (CVSS 6.5) affecting wordpress, gutenberg. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Auth. Stored (contributor+) Cross-Site Scripting (XSS) vulnerability in WordPress core 6.3 through 6.3.1, from 6.2 through 6.2.2, from 6.1 through 6.1.3, from 6.0 through 6.0.5, from 5.9 through 5.9.7 and Gutenberg plugin <= 16.8.0 versions.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.9% (top 41%)
CISA exploited list	No
Weakness	CWE-79
Published	2023-10-13
Last modified	2026-06-17

Publisher (CNA): Patchstack · Vendor: wordpress

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

Am I affected?

Timeline

2023-10-13 10:15 UTCPublished CVE record published
2026-06-17 06:09 UTCUpdated Record last modified

wordpress wordpress UPGRADE

Affected: >= 5.9 and <= 5.9.7 · >= 6.0 and <= 6.0.5 · >= 6.1 and <= 6.1.3 · >= 6.2 and <= 6.2.2 · >= 6.3 and <= 6.3.1

Fixed in: newer than 6.3.1

Safe to downgrade to: a release before 5.9

1. Check installed version

apt-cache policy wordpress || rpm -q wordpress || wordpress --version

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

sudo apt update && sudo apt install --only-upgrade wordpress

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wordpress

Note

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

3. If no update is available yet, DOWNGRADE to a release before 5.9 (Debian / Ubuntu)

apt-cache madison wordpress sudo apt install wordpress=<VERSION_BEFORE_5.9> sudo apt-mark hold wordpress

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list wordpress sudo dnf downgrade wordpress-<VERSION_BEFORE_5.9> sudo dnf versionlock add wordpress

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.

wordpress gutenberg UPGRADE

Affected: <= 16.8.0

Fixed in: newer than 16.8.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy gutenberg || rpm -q gutenberg || gutenberg --version

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

sudo apt update && sudo apt install --only-upgrade gutenberg

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade gutenberg

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

wordpress: upgrade to newer than 6.3.1; gutenberg: upgrade to newer than 16.8.0. Exact commands for each OS are on this page.

Is CVE-2023-38000 being exploited?

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

CVE-2023-38000 affects wordpress, gutenberg. Severity is medium (CVSS 6.5). Auth. Stored (contributor+) Cross-Site Scripting (XSS) vulnerability in WordPress core 6.3 through 6.3.1, from 6.2 through 6.2.2, from 6.1 through 6.1.3, from 6.0 through 6.0.5, from 5.9 through 5.9.7 and Gutenberg plugin <= 16.8.0 versions

How urgent is CVE-2023-38000?

Priority 42/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2026-63030 CRITICAL 9.8 EXPLOITED UPGRADE WordPress Core Interpretation Conflict Vulnerability
CVE-2026-60137 MEDIUM 5.9 EXPLOITED UPGRADE WordPress Core SQL Injection Vulnerability
CVE-2023-39999 MEDIUM 4.3 UPGRADE MITIGATE Exposure of Sensitive Information to an Unauthorized Actor in WordPress from 6.3 through 6.3.1, from 6.2 throu
CVE-2026-87902 HIGH 8.1 EXPLOITED UPGRADE WordPress Core Remote File Inclusion Vulnerability
CVE-2024-4439 HIGH 7.2 UPGRADE WordPress Core is vulnerable to Stored Cross-Site Scripting via user display names in the Avatar block in vari

References

← Back to latest CVEs