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

CVE-2026-2569

MEDIUM · 6.4 CVSS v3.1 Published 2026-03-11
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 Dear Flipbook – PDF Flipbook, 3D Flipbook, PDF embed, PDF viewer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via PDF page labels in all versions up to, and including, 2.4.20 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-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 Dear Flipbook WordPress plugin (versions up to 2.4.20) contains a stored XSS vulnerability in its PDF page label functionality. Authenticated attackers with Author-level permissions or higher can inject malicious JavaScript through insufficiently sanitized input, which executes when other users access the affected flipbook pages due to missing output escaping.

MitigationUpdate the Dear Flipbook plugin to the latest version once available, which should include proper input sanitization for PDF page labels and output escaping. Until then, restrict user account creation privileges and consider disabling the plugin if Author-level users are untrusted.

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. Confirm Dear Flipbook plugin is installed
    Navigate to WordPress Admin > Plugins and look for 'Dear Flipbook' in the plugin list. Note the installed version number shown on the plugin page.
    Affected if The plugin is installed and the version is 2.4.20 or lower (any version up to and including 2.4.20 is affected)
  2. Verify the plugin version against affected range
    In the plugins list, the version column displays the installed version. Compare this against 2.4.20 - any version at or below this number is within the vulnerable range.
    Affected if Installed version is 2.4.20 or lower
  3. Determine if PDF page label functionality is in use
    Check flipbook configurations by examining any flipbooks that have custom PDF page labels defined. This may be visible in the flipbook edit screen under PDF settings or page label fields.
    Affected if Any flipbook has custom PDF page labels configured and the plugin version is 2.4.20 or lower
  4. Identify users with Author-level or higher access
    Go to WordPress Admin > Users and review the role column. Users listed with Author, Editor, or Administrator roles have the permission level required to exploit this vulnerability.
    Affected if There are user accounts with Author, Editor, or Administrator roles and the plugin version is 2.4.20 or lower

You are affected if the Dear Flipbook plugin version is 2.4.20 or lower, PDF page labels are configured on any flipbook, and untrusted Author-level or higher users have access to the WordPress admin.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Dear Flipbook plugin to the latest version once available, which should include proper input sanitization for PDF page labels and output escaping. Until then, restrict user account creation privileges and consider disabling the plugin if Author-level users are untrusted.

Recommended fix Moderate confidence

Version 2.4.21 or later (check WordPress plugin repository for latest release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Dear Flipbook' plugin
  4. Check if an update is available (the vulnerability is patched in versions after 2.4.20)
  5. If an update is available, click 'Update Now' to install the latest version
  6. If no update shows, manually download the latest version from the WordPress plugin repository at plugins.trac.wordpress.org and upload/install it
  7. After updating, verify the plugin is running version 2.4.21 or higher
Caveat Review plugin settings after upgrade as with any plugin update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2569 — 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-2569 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