CVE-2026-7662
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 · uneditedThe ePaperFlip Publisher plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'publicationid' attribute of the `epaperflip_embed` shortcode in all versions up to, and including, 1. This is due to insufficient input sanitization and output escaping on the shortcode attribute which is injected directly into inline JavaScript. 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 confidenceThe ePaperFlip Publisher WordPress plugin has a stored XSS vulnerability in the `epaperflip_embed` shortcode's `publicationid` parameter. Due to insufficient input sanitization and output escaping, user-supplied data is directly embedded into inline JavaScript contexts, allowing authenticated attackers with Contributor-level access or higher to inject malicious scripts that execute whenever users access the affected page.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify ePaperFlip Publisher plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'ePaperFlip Publisher' or check the plugin files in wp-content/plugins/ for a folder containing 'epaperflip' or 'paperflip' in the nameAffected if The plugin is present on the site
-
Determine installed plugin versionIn WordPress admin_plugins page, click the plugin name link or view the plugin's main PHP file header for the Version: X.X tagAffected if Version is 1 or lower (the affected range is up to version 1)
-
Identify pages using the vulnerable shortcodeSearch the WordPress database or wp_posts table for content containing the string 'epaperflip_embed' using a tool like phpMyAdmin or WP-CLI: wpdb get_var("SELECT ID FROM wp_posts WHERE post_content LIKE '%epaperflip_embed%' AND post_status='publish'")Affected if The shortcode is present in published content
-
Inspect shortcode attributes for injectionExamine the shortcode usage found in post content - look for patterns like [epaperflip_embed publicationid="..."] and verify if the publicationid value contains quotes, script tags, or javascript: URLsAffected if The publicationid attribute contains unescaped special characters, quotes, or suspicious patterns that could indicate exploitation
A site is affected if the ePaperFlip Publisher plugin version 1 or lower is installed AND the epaperflip_embed shortcode is being used in published content with an unsanitized publicationid attribute.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the plugin to a patched version once available, or remove the `epaperflip_embed` shortcode from published content until a fix is released. Apply proper input sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_js, htmlspecialchars) before embedding user input into JavaScript contexts.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7662 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-7662 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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