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

CVE-2025-23922

CRITICAL · 10.0 CVSS v3.1 Published 2025-01-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Harsh iSpring Embedder embed-ispring allows Upload a Web Shell to a Web Server.This issue affects iSpring Embedder: from n/a through <= 1.0.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the iSpring Embedder WordPress plugin allows remote attackers to trick authenticated administrators into uploading malicious files, including web shells, by forging state-changing requests. Successful exploitation grants the attacker remote code execution on the server.

MitigationImplement anti-CSRF tokens (nonces) on all form submissions and AJAX actions that perform file uploads; add proper server-side file type validation and upload directory restrictions to prevent execution of uploaded files.

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
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

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. Identify iSpring Embedder plugin installation and version
    In WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'iSpring Embedder' in the list. Note the version number displayed. Alternatively, check the plugin files in wp-content/plugins/ for a version definition.
    Affected if The plugin is installed and its version falls within any known affected version range (compare your installed version to the official WordPress plugin repository for patch information).
  2. Verify file upload functionality exists
    Check the plugin settings page for any file upload or presentation embedding features. Look for forms that accept file uploads (typically for uploading iSpring presentations). Inspect the HTML source of these forms for the presence of file input fields.
    Affected if The plugin has an active file upload feature accessible to administrators.
  3. Inspect upload forms for anti-CSRF nonce fields
    View the source code of the plugin's admin pages containing file upload forms. Search for WordPress nonce fields (typically named '_wpnonce' or 'nonce' or created via wp_nonce_field()). Check if these nonces are properly validated on form submission.
    Affected if The upload forms lack proper anti-CSRF nonce tokens, or the submitted nonces are not validated server-side.
  4. Check server-side file type validation
    Review the plugin's PHP code that handles file uploads (typically in the main plugin file or a dedicated upload handler). Look for server-side checks that validate file types, extensions, and MIME types before allowing the upload.
    Affected if The upload handler performs no or inadequate server-side file type validation.
  5. Audit upload directories for suspicious files
    Check the WordPress uploads directory (wp-content/uploads/) and any plugin-specific upload folders for recently added executable files (.php, .phtml, .exe, .sh) or files with double extensions. Review access logs for unusual POST requests to upload endpoints.
    Affected if Unexpected PHP or executable files are present in upload directories, indicating possible exploitation.

If the iSpring Embedder plugin is installed with a vulnerable version lacking proper CSRF protection on file upload forms, and an authenticated administrator can be tricked into submitting a forged request, the environment is affected by this vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (nonces) on all form submissions and AJAX actions that perform file uploads; add proper server-side file type validation and upload directory restrictions to prevent execution of uploaded files.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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