# CVE-2025-23922: WordPress iSpring Embedder plugin <= 1.0 - CSRF to Arbitrary File Upload vulnerability

> A CSRF vulnerability in the iSpring Embedder WordPress plugin allows attackers to upload arbitrary files, potentially leading to remote code execution.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jan 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-226x-xgh7-2wwc

## What is CVE-2025-23922?

CVE-2025-23922 is a critical vulnerability in Harsh iSpring Embedder, published on 16 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2025-23922?


## How do I fix CVE-2025-23922?

No fix has been published for CVE-2025-23922 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-23922 being exploited?

There is no known exploitation of CVE-2025-23922 in the wild and no public exploit code.

Public exploit code:

- WordPress iSpring Embedder plugin <= 1.0 - CSRF to Arbitrary File Upload vulnerability (github_poc): https://github.com/Nxploited/CVE-2025-23922

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-23922 and fix it if it is affected.

What it is: CVE-2025-23922 is a critical vulnerability in Harsh iSpring Embedder, published on 16 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-23922 in the wild and no public exploit code.

Affected product: Harsh iSpring Embedder. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-23922/ (Markdown: https://insights.sbomify.com/CVE-2025-23922/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-23922
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-23922
- OSV: https://osv.dev/vulnerability/CVE-2025-23922

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-23922/
Summaries are generated and may contain mistakes; the official description above is the record.