dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-7796

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The EmbedPress – PDF Embedder, Embed PDF viewer, YouTube Videos, 3D FlipBook, Social feeds & more plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the block 'url' attribute in all versions up to, and including, 4.5.3 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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The EmbedPress WordPress plugin suffers from a stored XSS vulnerability in its block's 'url' attribute. Authenticated users with contributor-level access can inject malicious JavaScript via the url parameter due to insufficient input sanitization and output escaping, which executes when other users view the affected pages.

MitigationUpdate the EmbedPress plugin to version 4.5.4 or later. Review existing content for any injected scripts and remove them. Implement role-based access controls to limit who can create/edit content using the plugin blocks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify EmbedPress plugin is installed
    Log in to WordPress admin panel and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for the embedpress folder
    Affected if The EmbedPress plugin is present in the WordPress installation
  2. Check installed version of EmbedPress
    In WordPress admin, go to Plugins > Installed Plugins and locate EmbedPress to view the version number, or inspect the main plugin file header in /wp-content/plugins/embedpress/embedpress.php
    Affected if The installed version is 4.5.3 or earlier
  3. Identify use of embed blocks with url attribute
    Review pages and posts for EmbedPress blocks that contain a url parameter, particularly in content created by contributor-level or higher users
    Affected if EmbedPress embed blocks with url attributes are present in published content
  4. Inspect embed block content for unsanitized input
    Use WordPress block editor to view the raw block data or query the wp_posts table for content containing embedpress-related shortcodes or blocks with url parameters
    Affected if The url attribute in embed blocks contains unescaped or raw URLs without proper sanitization patterns

A user is affected if EmbedPress plugin version 4.5.3 or earlier is installed AND embed blocks with url attributes exist in published content, allowing stored XSS injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the EmbedPress plugin to version 4.5.4 or later. Review existing content for any injected scripts and remove them. Implement role-based access controls to limit who can create/edit content using the plugin blocks.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7796 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7796 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data