dbcve.org
Wp Flow PlusWordPress extension · Spiffyplugins

CVE-2024-49695

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-24
Fix available
A fix is available. Upgrade to 5.2.4 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 ('Cross-site Scripting') vulnerability in Spiffy Plugins WP Flow Plus wp-imageflow2 allows Stored XSS.This issue affects WP Flow Plus: from n/a through <= 5.2.3.

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

Stored Cross-site Scripting (XSS) vulnerability in the WP Flow Plus WordPress plugin's wp-imageflow2 component allows authenticated attackers to inject malicious JavaScript that persists in the database and executes when users view affected pages.

MitigationUpdate WP Flow Plus to the latest patched version. Until then, disable the wp-imageflow2 component or restrict administrative access to minimize exposure to authenticated attackers.

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.4

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. Verify WP Flow Plus plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for the wp-flow-plus folder
    Affected if The WP Flow Plus plugin by Spiffyplugins is present on the WordPress site
  2. Check installed version against vulnerable range
    In WordPress admin, view the plugin details to see the version number, or check the main plugin file (e.g., wp-flow-plus.php) for the Version header
    Affected if The installed version is lower than 5.2.4 (e.g., 5.2.3, 5.2.0, etc.)
  3. Confirm wp-imageflow2 component is in use
    Check pages, posts, or widgets that utilize the [wp-imageflow2] shortcode, or inspect the plugin settings for active imageflow2 configurations
    Affected if The wp-imageflow2 shortcode or component is actively used on any published content
  4. Inspect plugin settings for suspicious stored content
    Navigate to WP Flow Plus settings in WordPress admin, and examine any fields that store image captions, titles, or custom text for unexpected script tags or HTML
    Affected if Any fields contain raw script tags, javascript: URLs, or on* event handlers that were not intentionally added by an administrator

You are affected if WP Flow Plus version is below 5.2.4 AND the wp-imageflow2 component is actively used on your site, as this creates the attack surface for stored XSS injection and execution.

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.4 or later
Fixed in 5.2.4
Interim mitigation

Update WP Flow Plus to the latest patched version. Until then, disable the wp-imageflow2 component or restrict administrative access to minimize exposure to authenticated attackers.

Recommended fix High confidence

5.2.4

  1. 1. Create a complete backup of your WordPress site before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Find WP Flow Plus in the plugin list.
  4. 4. Click 'Update Now' if an update is available, or manually upload version 5.2.4 of the plugin from the WordPress Plugin Repository.
  5. 5. After updating, verify the plugin is running version 5.2.4 in the Plugins list.
  6. 6. Test the wp-imageflow2 functionality to ensure it works correctly after the update.

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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