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

CVE-2025-46524

HIGH · 7.1 CVSS v3.1 Published 2025-04-24
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 stesvis WP Filter Post Category wp-filter-post-categories allows Stored XSS.This issue affects WP Filter Post Category: from n/a through <= 2.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 WP Filter Post Category plugin (wp-filter-post-categories) allows unauthenticated attackers to craft malicious requests that result in Stored XSS. The lack of proper nonce validation on form submissions and AJAX endpoints enables attackers to inject persistent malicious scripts that execute when users view affected content.

MitigationUpdate to the latest patched version of the plugin when available. Until a patch is released, disable or remove the plugin, or implement web application firewall rules to block malicious requests targeting the affected endpoints.

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. Verify the plugin is installed
    Navigate to WordPress admin > Plugins and look for 'WP Filter Post Category' or 'wp-filter-post-categories' in the installed plugins list
    Affected if The plugin appears in the installed plugins list
  2. Check the installed version
    In the Plugins page, click on the plugin to view its details or inspect the plugin header in wp-content/plugins/wp-filter-post-categories/wp-filter-post-categories.php for the Version field
    Affected if Any version is installed since no patched version is specified in the advisory
  3. Confirm the plugin is active
    In WordPress admin > Plugins, check if the plugin is activated (the 'Activate' link should show 'Deactivate')
    Affected if The plugin is currently activated
  4. Inspect for stored XSS payloads
    Check post categories, taxonomy terms, or any content created through the plugin's frontend forms for suspicious script tags or event handlers (search for <script, javascript:, onerror=, onload= in wp_terms or wp_term_taxonomy database tables if accessible)
    Affected if Any unrecognized or malicious script tags exist in category or taxonomy data
  5. Check AJAX endpoints for nonce protection
    Examine the plugin PHP files in wp-content/plugins/wp-filter-post-categories for AJAX handlers (wp_ajax_ and wp_ajax_nopriv_ hooks) and verify if they validate nonces using check_ajax_referer or wp_verify_nonce
    Affected if AJAX endpoints lack nonce validation code (the check_ajax_referer or wp_verify_nonce function calls are missing)

If the WP Filter Post Category plugin is installed and active with any version, the lack of nonce validation on form submissions means the environment is vulnerable to CSRF-induced stored XSS attacks.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest patched version of the plugin when available. Until a patch is released, disable or remove the plugin, or implement web application firewall rules to block malicious requests targeting the affected endpoints.

Recommended fix Moderate confidence

latest available version (newer than 2.1.4)

  1. Log into the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'WP Filter Post Category' by stesvis
  4. Check if an update is available - if so, update to the latest version
  5. If no update is available in the WordPress repository, manually download the latest version from the official WordPress plugin repository and reinstall

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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