dbcve.org
Wp Flow PlusWordPress extension · Spiffyplugins

CVE-2024-35651

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-04
Fix available
A fix is available. Upgrade to 5.2.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Spiffy Plugins WP Flow Plus allows Stored XSS.This issue affects WP Flow Plus: from n/a through 5.2.2.

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 · moderate confidence

This is a stored Cross-Site Scripting (XSS) vulnerability in the WP Flow Plus WordPress plugin. The vulnerability allows an attacker to inject malicious JavaScript code through unsanitized user input, which is then stored on the server and executes when other users view the affected content in the WordPress admin dashboard or public-facing pages.

MitigationUpdate WP Flow Plus to the latest patched version once available. In the interim, sanitize all user inputs using WordPress sanitization functions (such as sanitize_text_field(), esc_attr(), and esc_html()) before outputting data, and implement Content Security Policy headers to mitigate XSS execution.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp Flow PlusWordPress extension
Affected:< 5.2.3

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 WP Flow Plus plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Flow Plus' or 'Spiffyplugins Wp Flow Plus' in the list
    Affected if The plugin is installed and active
  2. Identify the installed plugin version
    Click 'View Details' on the WP Flow Plus plugin in the WordPress plugins list to reveal the version number
    Affected if Version is lower than 5.2.3 (for example, 5.2.2, 5.2.1, 5.2.0, or earlier)
  3. Identify plugin settings pages that accept user input
    Navigate to the WP Flow Plus settings area in the WordPress admin sidebar (usually under Settings or a dedicated WP Flow Plus menu) and locate any text input fields, textarea fields, or configuration options that store user-submitted values
    Affected if The plugin has input fields where custom text or settings can be entered and saved to the database
  4. Inspect stored data for unsanitized script tags
    Access the WordPress database via phpMyAdmin or WP-CLI and query the wp_options table or any custom tables created by the plugin for suspicious script tags, such as <script> or javascript: URIs, in fields related to WP Flow Plus settings
    Affected if Database entries contain raw HTML or script tags that were not escaped or sanitized upon storage
  5. Review admin dashboard and public pages for injected scripts
    View the WP Flow Plus admin pages and any public-facing pages where the plugin displays user-configured content. Use browser developer tools to inspect the page source for unexpected script tags or event handlers (onload, onerror, onclick) in plugin-generated elements
    Affected if Injected malicious JavaScript code is present and executes when viewing plugin-related pages

You are affected if the WP Flow Plus plugin version is installed and it is lower than 5.2.3, and the plugin settings contain unsanitized user input that could be exploited for stored XSS.

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
Upgrade available Upgrade to 5.2.3 or later
Fixed in 5.2.3
Interim mitigation

Update WP Flow Plus to the latest patched version once available. In the interim, sanitize all user inputs using WordPress sanitization functions (such as sanitize_text_field(), esc_attr(), and esc_html()) before outputting data, and implement Content Security Policy headers to mitigate XSS execution.

Recommended fix Moderate confidence

5.2.3

  1. Backup the WordPress site and database before performing any updates
  2. Update the WP Flow Plus plugin to version 5.2.3 or later through the WordPress admin dashboard (Plugins > WP Flow Plus > Update Now)
  3. Alternatively, update via FTP or hosting control panel by uploading the new plugin version
  4. Verify the update was successful by checking the plugin version in the WordPress admin (Plugins > Installed Plugins > WP Flow Plus)
  5. Clear any site caches if caching plugins are in use to ensure the fixed code is served

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

Fix this in Wp Flow Plus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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