Security readout for executives and security teams
Plain-English summary
This affects WordPress sites using WP Calais Auto Tagger version 2.0 or earlier. A successful attack could trick an authenticated user into causing stored script content in the site, creating confidentiality, integrity, and availability impact. The sources rate it high severity, but do not show CISA KEV listing or active exploitation.
Executive priority
Treat as a high-priority WordPress plugin exposure if the plugin is present. Prioritize inventory first; if affected installations exist, reduce exposure quickly because stored XSS can damage visitor trust and site integrity.
Technical view
CVE-2025-32563 is a CSRF issue in dangrossman WP Calais Auto Tagger, reported as CSRF to stored XSS, affecting versions through 2.0. The CVSS 3.1 score is 7.1 with network attack vector, low complexity, no privileges, and required user interaction. No fixed version is provided in the supplied sources.
Likely exposure
Exposure is limited to WordPress installations where the calais-auto-tagger plugin is installed at version 2.0 or earlier. The bundle does not establish exposure for other WordPress plugins, themes, or core WordPress.
Exploitation context
The vulnerability requires user interaction and is not listed as CISA KEV in the supplied data. The public bundle describes the vulnerability class and impact but does not provide evidence of active exploitation, public exploit availability, or observed campaigns.
Researcher notes
The source data identifies CWE-352 and describes CSRF leading to stored XSS, but does not include patch details, exploit telemetry, or proof-of-concept status. Avoid assuming broader product impact or a fixed release until vendor or database guidance states it.
Mitigation direction
- Inventory WordPress sites for WP Calais Auto Tagger installations.
- Disable or remove affected versions until vendor guidance confirms a safe path.
- Check Patchstack and CVE records for fixed-version or workaround updates.
- Restrict WordPress administrative access to trusted users and sessions.
- Review recent site content changes for unexpected injected script content.
Validation and detection
- Confirm whether calais-auto-tagger is installed on each WordPress site.
- Record installed plugin versions and flag versions 2.0 or earlier.
- Review plugin settings and affected content areas for unexpected changes.
- Check logs for unusual authenticated administrative actions.
- Track CVE and Patchstack updates for remediation changes.
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-32563 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
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/Wordpress/Plugin/calais-auto-tagger/vulnerability/wordpress-wp-calais-auto-tagger-plugin-2-0-csrf-to-stored-xss-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
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.