PDF Embedder <= 4.9.3 - Authenticated (Contributor+) Information Exposure via Block Editor Page
Strategic Overview
- Status
- Patched in 5.0.0
- Affected Plugin
- PDF Embedder
- Affected Version
<= 4.9.3- CVSS
- 4.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-7526
At a glance
CVE-2026-7526 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the PDF Embedder WordPress plugin, affecting versions <= 4.9.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 5.0.0; sites on affected versions should update now. Disclosed May 2026, reported by Dmitrii Ignatyev.
Vulnerability Overview
The PDF Embedder plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.9.3 via the enqueue_block_assets. This makes it possible for authenticated attackers, with contributor-level access and above, to extract configuration data. License key exposure occurs when the premium add-on is also installed and has saved a key; on Lite-only installations, the exposed data is limited to non-sensitive viewer configuration values such as width, height, toolbar settings, usage tracking, and plan.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in PDF Embedder <= 4.9.3 takes an account at Contributor level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For PDF Embedder the fix is 5.0.0: builds <= 4.9.3 are affected, anything from 5.0.0 onward is not.
Remediation
Update to version 5.0.0, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: PDF Embedder 5.0.0 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C