CVE-2024-11929
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 Responsive FlipBook Plugin Wordpress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the rfbwp_save_settings() functionin all versions up to, and including, 2.5.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Subscriber-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 Responsive FlipBook Plugin for WordPress is vulnerable to stored XSS via the rfbwp_save_settings() function in versions up to 2.5.0. Authenticated attackers with Subscriber-level access can inject arbitrary JavaScript through unsanitized plugin settings, which executes when other users access affected pages.
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.
-
Confirm plugin installation and versionNavigate to WordPress Admin > Plugins and locate 'Responsive FlipBook' or 'rfbwp'. Note the installed version number.Affected if The plugin is installed and the version is 2.5.0 or lower.
-
Identify subscriber-level user accountsGo to WordPress Admin > Users and review the user list. Check the 'Role' column for any accounts with 'Subscriber' role.Affected if Any subscriber-level accounts exist on the site.
-
Check plugin settings for subscriber accessAttempt to access the plugin settings page (typically under FlipBook or rfbwp menu) using a subscriber account, or inspect the plugin code for capability checks on the rfbwp_save_settings function.Affected if Subscriber role can access or submit plugin settings.
-
Inspect plugin settings for injected scriptsExamine the plugin's saved settings in the WordPress database (wp_options table, look for rfbwp_ prefixed options) or the plugin settings UI. Look for unexpected HTML tags, script elements, or javascript: protocols in any text fields.Affected if Any plugin settings contain script tags, event handlers, or javascript: URLs.
A user is affected if the Responsive FlipBook plugin version 2.5.0 or lower is installed AND subscriber-level accounts exist with access to plugin settings.
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 to the latest patched version of the plugin once available. In the interim, restrict subscriber-level user permissions and review existing user accounts.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11929 — 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-2024-11929 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