CVE-2025-23446
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in KokoenDE WP SpaceContent wp-spacecontent allows Stored XSS.This issue affects WP SpaceContent: from n/a through <= 0.4.5.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the WP SpaceContent WordPress plugin allows attackers to inject malicious scripts through forged requests, resulting in Stored XSS. The plugin lacks proper anti-CSRF tokens on state-changing operations, enabling attackers to trick authenticated administrators into executing unintended actions that persist malicious content.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP SpaceContent plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'WP SpaceContent' in the list of active plugins.Affected if WP SpaceContent plugin is present and active in the WordPress installation.
-
Identify installed plugin versionIn the Plugins list, click on WP SpaceContent to view the plugin details, or inspect the plugin header in /wp-content/plugins/space-content/ directory for the 'Version' comment.Affected if The installed version has not been patched for CSRF vulnerabilities (compare against the vendor's patched version once available).
-
Inspect admin-ajax.php usage for state-changing actionsReview plugin PHP files in /wp-content/plugins/space-content/ for 'admin-ajax.php' hooks (add_action calls with 'wp_ajax_') and check if these endpoints perform state-changing operations without nonce verification.Affected if The plugin performs database writes, content updates, or settings changes via admin-ajax without proper nonce/CSRF token validation.
-
Check form submissions for CSRF token presenceExamine plugin PHP files for form generation code (rendering forms in admin pages) and verify if wp_nonce_field or similar anti-CSRF functions are used.Affected if Forms that modify plugin settings, content, or state do not include nonce verification tokens.
-
Audit stored content for injected scriptsQuery the WordPress database (wp_posts, wp_postmeta, or custom tables created by the plugin) for any suspicious script tags, iframe elements, or event handlers in content fields that were not intentionally added by administrators.Affected if Malicious JavaScript or iframe tags are stored in plugin-related database tables without legitimate admin origin.
A user is affected if the WP SpaceContent plugin is installed and performs state-changing operations (forms, admin-ajax endpoints) without CSRF token validation, or if malicious scripts are found stored in the database.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate WP SpaceContent to the latest version after confirmation of patch availability; if no patch exists, implement anti-CSRF tokens on all form submissions and admin-ajax endpoints, and apply proper input sanitization and output encoding for all user-supplied data.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23446 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-23446 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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