dbcve.org
Modal WindowWordPress extension · Wow Company

CVE-2025-24717

HIGH · 8.8 CVSS v3.1 Published 2025-01-24
Fix available
A fix is available. Upgrade to 6.1.5 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Wow-Company Modal Window modal-window allows Cross Site Request Forgery.This issue affects Modal Window: from n/a through <= 6.1.4.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Wow-Company Modal Window plugin (versions <= 6.1.4) allows attackers to trick authenticated users into unknowingly submitting malicious requests to the affected application. The vulnerability exists because the plugin does not properly validate the origin of requests, enabling attackers to forge state-changing actions on behalf of victims.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations, validate Origin/Referer headers server-side, and set SameSite attribute on session cookies to prevent cross-site request forgery.

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
Modal WindowWordPress extension
Affected:< 6.1.5

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 the installed version of the Wow Company Modal Window plugin
    Access your WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'Wow Company Modal Window', and note the version number displayed. Alternatively, inspect the plugin's main PHP file or readme.txt to find the Version header.
    Affected if The displayed version is lower than 6.1.5 (for example, 6.1.4, 6.1.0, or any version number below 6.1.5).
  2. Confirm the plugin is active
    In the WordPress admin under Plugins > Installed Plugins, verify that Wow Company Modal Window shows as 'Active' rather than 'Inactive'. The vulnerability only applies when the plugin is enabled.
    Affected if The plugin is currently active with a version below 6.1.5.
  3. Inspect admin forms for anti-CSRF tokens
    Navigate to the plugin's settings pages (typically under a menu item like 'Modal Window' or 'Wow Company'). Open your browser's developer tools (F12), go to the Network tab, and examine state-changing forms (such as those for saving modal settings, creating new modals, or updating configurations). View the HTML source of these forms to check for the presence of nonce fields (look for input elements with type='hidden' containing names like '_wpnonce', 'nonce', or similar security tokens.
    Affected if The plugin's admin forms lack anti-CSRF nonce tokens or token validation logic in the affected version range.

You are affected if the Wow Company Modal Window plugin is active and its installed version is below 6.1.5, as this version range lacks proper anti-CSRF protection on state-changing administrative actions.

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 6.1.5 or later
Fixed in 6.1.5
Interim mitigation

Implement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations, validate Origin/Referer headers server-side, and set SameSite attribute on session cookies to prevent cross-site request forgery.

Recommended fix High confidence

6.1.5

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Modal Window' plugin by Wow-Company
  4. 4. If an update is available, click 'Update Now' to upgrade to version 6.1.5
  5. 5. Alternatively, go to Dashboard > Updates and select the Modal Window plugin for update
  6. 6. After updating, verify the plugin version shows 6.1.5

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

Fix this in Modal Window Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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