Live › vulnerability › CVE-2026-109370
Go to dashboardThe Document Embedder WordPress plugin up to and including 2.4.0 does not sanitize block JSON in post content, so a contributor can store a malicious link. When a visitor clicks the embedded document's Download button, attacker script runs in their browser.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 07:31 UTC. All times on this page are UTC.
Sites running Document Embedder 2.4.0 or earlier where contributors or higher can publish or edit pages with embedded documents. Visitors to those pages are the victims. Sites without the plugin, or where only trusted editors write content, have lower exposure.
No product ranges from the sources yet.
wp plugin get document-embedder --field=versiondocumentSource.doc2.4.0 once a patched release is listed in the sources (the sources do not name one: unknown)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The Document Embedder – let visitors read files without downloading plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'content (post_content containing block JSON documentSource.doc)' parameter in all versions up to, and including, 2.4.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload is triggered specifically when the victim clicks the embedded document's Download button, which causes the de_track_download AJAX fallback path to programmatically create an anchor with the attacker-controlled href and call .click() — a condition reached because supplying docId=0 causes can_read_document() to return false, bypassing the normal download flow.
This page as .md · .json · in your agent: get_signal("CVE-2026-109370")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.