Security readout for executives and security teams
Plain-English summary
CVE-2025-23446 affects the WordPress WP SpaceContent plugin up to version 0.4.5. A malicious site could abuse CSRF to cause stored cross-site scripting if a targeted user interacts with it. Business risk is highest for WordPress sites using this plugin, especially where administrators handle content or settings in active sessions.
Executive priority
Treat as high priority for any public or business-critical WordPress site using WP SpaceContent. Prioritize inventory and removal or vendor-guided remediation because stored XSS can affect visitors and administrators, but current sources do not confirm active exploitation.
Technical view
The vulnerability is a CSRF issue in KokoenDE WP SpaceContent wp-spacecontent that can lead to stored XSS. CVSS 3.1 is 7.1 high: network reachable, low complexity, no attacker privileges, user interaction required, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress installations with WP SpaceContent installed at version 0.4.5 or earlier. The bundle does not identify affected CPEs or hosting platforms beyond the plugin package name wp-spacecontent.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Attack success requires user interaction, consistent with CSRF and the CVSS UI:R rating. Stored XSS can persist in site content or plugin-managed data after the triggering action.
Researcher notes
Evidence supports CSRF leading to stored XSS in WP SpaceContent through 0.4.5. Do not assume a patch version from the provided sources. Validation should focus on version presence, plugin-managed stored data, and whether official vendor or Patchstack remediation becomes available.
Mitigation direction
Inventory WordPress sites for the WP SpaceContent plugin and installed version.
Disable or remove WP SpaceContent where it is unnecessary or outdated.
Check Patchstack and vendor guidance for any fixed version or official mitigation.
Limit administrative browsing while logged in until exposure is resolved.
Review WordPress administrator accounts for suspicious changes after suspected exposure.
Validation and detection
Confirm whether wp-spacecontent is installed on each WordPress instance.
Record the plugin version and flag 0.4.5 or earlier.
Review plugin-managed content and settings for unexpected script-like changes.
Check security tooling for alerts tied to stored XSS or WordPress content modification.
Document whether a vendor-approved fix or removal action was applied.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
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.
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.
We 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.