Sensitive Information Exposure in WordPress: CVE-2023-39999

wordpress Updated 02 Oct 2025

Summary

13/10/2023
N/A
Yes i
Medium
4.3

CVE-2023-39999: Exposure of Sensitive Information to an Unauthorized Actor in WordPress from 6.3 through 6.3.1, from 6.2 through 6.2.2, from 6.1 through 6.13, from 6.0 through 6.0.5, from 5.9 through 5.9.7, from 5.8 through 5.8.7, from... Affects wordpress across 3 version ranges.

>= 4a6363076129378869f8742ef00a39a7421e6f29, < e8676f6226fb01cd17222c771717969f42e73505 < 5.7.11+dfsg1-0+deb11u1 >= ac3899153a790a6f060dc816ff94812e0fd99875, < ffb401296259cc20eed753bf0f934221df45e32e

Fixed in 5.7.11+dfsg1-0+deb11u1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

WordPress is a widely-used open-source content management system (CMS) that allows users to create and manage websites easily. It is known for its flexibility, extensibility through plugins, and a large community of developers. However, like any software, it is susceptible to vulnerabilities that can compromise its security. CVE-2023-39999 affects multiple versions of WordPress, exposing sensitive information to unauthorized actors, which can lead to data breaches and unauthorized access.

Vulnerability Detail

CVE-2023-39999 is a vulnerability that allows unauthorized actors to access sensitive information in WordPress installations. This issue arises from improper handling of sensitive data across various versions of WordPress, including versions from 4.1 to 6.3.1. The potential ramifications include unauthorized access to user data, which can lead to identity theft, data manipulation, and loss of user trust. The vulnerability has a CVSS score of 4.3, indicating a moderate level of risk.

How To Fix

Minimum fixed version

5.7.11+dfsg1-0+deb11u1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade wordpress

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If immediate updating is not feasible, users can implement access controls to limit exposure to sensitive information. This can include:

  1. Restricting access to the WordPress admin area to trusted IP addresses.
  2. Using security plugins to monitor and block unauthorized access attempts.
  3. Regularly reviewing user roles and permissions to ensure only necessary access is granted.

Conclusion

CVE-2023-39999 is a significant vulnerability affecting multiple versions of WordPress, exposing sensitive information to unauthorized actors. Users are strongly advised to update their installations to the latest versions to mitigate risks. Implementing access controls can serve as a temporary measure until updates are applied.

See every vulnerability recorded for wordpress →

Share this vulnerability

FAQ

CVE-2023-39999 is a vulnerability in WordPress that allows unauthorized access to sensitive information across multiple versions.

The vulnerability affects WordPress versions from 4.1 to 6.3.1.

The risks include unauthorized access to user data, identity theft, data manipulation, and loss of user trust.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities. Check your application using the Vulert playground at Vulert Scanner.

Implement access controls and security measures to limit exposure to sensitive information until you can update.

Related vulnerabilities

Recent vulnerabilities recorded for wordpress.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Minimum fixed version

5.7.11+dfsg1-0+deb11u1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade wordpress

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback