Security readout for executives and security teams
Plain-English summary
CVE-2025-46524 affects the WordPress WP Filter Post Category plugin through version 2.1.4. A CSRF flaw can lead to stored cross-site scripting, meaning malicious script could be saved in the site and later run in a user’s browser. The provided sources do not name a fixed version.
Executive priority
Treat this as a high-priority WordPress plugin exposure check, especially for customer-facing sites. The main business risk is stored browser-side script execution affecting users or administrators. Because no fixed version is named in the provided evidence, prioritize inventory, removal where feasible, and close monitoring for vendor guidance.
Technical view
The CVE describes CWE-352 CSRF in stesvis WP Filter Post Category, package wp-filter-post-categories, enabling stored XSS. CVSS 3.1 is 7.1 high with network attack vector, low complexity, no attacker privileges, and required user interaction. The bundle does not identify the vulnerable endpoint, exploit details, or a patch release.
Likely exposure
Exposure is limited to WordPress sites with WP Filter Post Category/wp-filter-post-categories installed at version 2.1.4 or earlier. Sites without this plugin are not indicated as affected. Prioritize externally managed WordPress estates, client sites, and sites with administrator sessions used from normal browsing environments.
Exploitation context
The provided bundle does not state active exploitation, and KEV is false. Exploitation would require user interaction consistent with CSRF and stored XSS risk. Because the public sources omit endpoint and patch details, assume uncertainty and avoid treating this as confirmed weaponized activity.
Researcher notes
Sources confirm CSRF to stored XSS but omit endpoint, nonce behavior, required victim role, proof-of-concept details, and fixed-version information. Validate only in authorized environments and avoid offensive reproduction steps. Research should focus on version identification, configuration exposure, and whether maintainers have published remediation guidance.
Mitigation direction
- Inventory WordPress sites for wp-filter-post-categories installations.
- Disable or remove the plugin where business impact is acceptable.
- Check vendor, WordPress, or Patchstack guidance for a fixed release.
- Upgrade promptly if an official fixed version becomes available.
- Limit administrator browsing sessions and enforce strong WordPress admin hygiene.
Validation and detection
- Confirm whether WP Filter Post Category is installed on each WordPress site.
- Record plugin versions and flag any version 2.1.4 or earlier.
- Review site content and plugin-managed fields for unexpected stored scripts.
- Check security monitoring for suspicious WordPress admin activity.
- Document compensating controls where removal is delayed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-46524 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.