dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-30912

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
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 Float menu float-menu allows Cross Site Request Forgery.This issue affects Float menu: from n/a through <= 6.1.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

Cross-Site Request Forgery (CSRF) vulnerability in the Wow-Company Float menu WordPress plugin (versions <= 6.1.2) allows attackers to induce authenticated users to perform unwanted state-changing actions on the plugin's admin interface.

MitigationUpdate to the patched version of Float menu when available; until then, implement anti-CSRF tokens on plugin forms and actions, and consider deploying SameSite cookie attributes.

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

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

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. Locate the Float menu plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'float-menu' or 'wow-company-float-menu', or use WP-CLI: wp plugin list --name='float-menu'
    Affected if The plugin folder or listing is found in the WordPress installation
  2. Verify the plugin is active
    Use WP-CLI: wp plugin is-active float-menu, or check the wp_options table for the active_plugins option, or inspect the WordPress admin plugins list
    Affected if The plugin appears in the list of active plugins
  3. Determine the installed version
    Inspect the plugin's main PHP file header (e.g., wp-content/plugins/float-menu/float-menu.php) for the 'Version' field, or use WP-CLI: wp plugin get float-menu --field=version
    Affected if The version number returned is 6.1.2 or lower
  4. Confirm admin interface has state-changing actions
    Review the plugin's admin menu entries and examine its admin PHP files (typically in an /admin/ subfolder) for form submissions ($_POST handling) or action URLs that perform modifications to plugin settings or data
    Affected if The plugin admin interface contains forms or action parameters that modify plugin state without visible CSRF token fields in the HTML

You are affected if the Float menu plugin is installed, active, and running at version 6.1.2 or lower, with its admin interface offering forms or actions that process state-changing requests.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the patched version of Float menu when available; until then, implement anti-CSRF tokens on plugin forms and actions, and consider deploying SameSite cookie attributes.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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