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

CVE-2025-58847

HIGH · 7.1 CVSS v3.1 Published 2025-09-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 Yaidier WN Flipbox Pro wn-flipbox-pro allows Reflected XSS.This issue affects WN Flipbox Pro: from n/a through <= 2.1.

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

A CSRF vulnerability in the Yaidier WN Flipbox Pro WordPress plugin (version <= 2.1) allows attackers to trick authenticated administrators into submitting malicious requests that trigger reflected XSS attacks, potentially leading to session hijacking or privilege escalation.

MitigationUpdate to the latest version of WN Flipbox Pro when available; otherwise implement anti-CSRF tokens on all plugin forms and verify Origin/Referer headers to block forged requests.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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. Confirm plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'wn-flipbox-pro', 'wn-flipbox', or search for 'Yaidier' or 'flipbox' in plugin names. Alternatively, list installed plugins via WP-CLI: wp plugin list --format=csv
    Affected if The 'wn-flipbox-pro' or related flipbox plugin folder exists in the plugins directory
  2. Identify installed version
    Read the main plugin PHP file (usually in the plugin folder, named like flipbox.php or index.php) and look for the 'Version' header in the plugin comment block. In WordPress admin, go to Plugins > Installed Plugins and find the version listed for WN Flipbox Pro
    Affected if The reported version is 2.1 or lower, or no version is displayed (indicating an old unversioned release)
  3. Verify plugin is active
    Check if the plugin is enabled in WordPress admin under Plugins > Installed Plugins. The plugin should show as 'Active'. Using WP-CLI: wp plugin is-active flipbox (adjust slug as needed)
    Affected if The plugin status shows as Active
  4. Inspect admin forms for CSRF protection
    Locate PHP files handling plugin admin actions (check folders like includes/, admin/, or files containing form handling). Search for 'nonce' or '_wpnonce' in the code to determine if form submissions include anti-CSRF tokens. Use grep: grep -r 'nonce' /path/to/plugin/folder/
    Affected if Admin action files (especially those handling settings or user input) lack nonce verification code or do not call wp_verify_nonce()
  5. Check for reflected XSS sink usage
    Examine PHP files for use of echo, print, or similar output functions that directly reflect request parameters without sanitization. Search for $_GET, $_POST usage with output: grep -E '\$_GET|\$_POST' /path/to/plugin/folder/*.php and verify if those values are sanitized with esc_html(), esc_attr(), or similar before output
    Affected if Request parameters from $_GET or $_POST are output directly without sanitization, combined with no CSRF protection means the full attack chain is present

If the Yaidier WN Flipbox Pro plugin is installed, active, and at version 2.1 or lower without nonce/CSRF protection on admin forms, the environment is vulnerable to CVE-2025-58847.

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 latest version of WN Flipbox Pro when available; otherwise implement anti-CSRF tokens on all plugin forms and verify Origin/Referer headers to block forged requests.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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