CVE-2026-5075
Received Received - Intake
Sensitive Information Exposure in All in One SEO WordPress Plugin

Publication date: 2026-05-20

Last updated on: 2026-05-20

Assigner: Wordfence

Description
The All in One SEO plugin for WordPress is vulnerable to Sensitive Information Exposure via 'internalOptions' localized script data in versions up to, and including, 4.9.7 due to sensitive internal option data being passed to wp_localize_script() in post editor contexts without effective masking for low-privilege users. This makes it possible for authenticated attackers, with contributor-level access and above, to view configured API/OAuth tokens and license-related values from page source.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-20
Last Modified
2026-05-20
Generated
2026-05-20
AI Q&A
2026-05-20
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
all_in_one_seo all_in_one_seo to 4.9.7 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The All in One SEO plugin for WordPress versions up to and including 4.9.7 has a vulnerability where sensitive internal option data is exposed via the 'internalOptions' localized script data. This happens because sensitive data is passed to the wp_localize_script() function in post editor contexts without proper masking for users with low privileges.

As a result, authenticated attackers with contributor-level access or higher can view sensitive information such as configured API/OAuth tokens and license-related values by inspecting the page source.


How can this vulnerability impact me? :

This vulnerability allows attackers with contributor-level access or above to access sensitive information like API/OAuth tokens and license-related data that should normally be protected.

Exposure of such sensitive tokens can lead to unauthorized access to external services or APIs, potentially compromising the security of the website or connected systems.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart