# CVE-2023-47350: Cross Site Request Forgery in SwiftyEdit


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Nov 2023
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-2492-xxqf-6h78

## What is CVE-2023-47350?

CVE-2023-47350 is a high-severity vulnerability in n/a, published on 22 Nov 2023. 

### Official description

Cross-Site Request Forgery (CSRF) vulnerability in SwiftyEdit Content Management System prior to v1.2.0, allows remote attackers to escalate privileges via the user password update functionality.

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

## Which versions are affected by CVE-2023-47350?

2 open source packages ship an affected version, including swiftyedit/swiftyedit. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `swiftyedit/swiftyedit` | Packagist | All versions | 1.2.0 |
| `swiftyedit/swiftyedit` | Packagist | All versions | 1.2.0 |

Products: Swiftyedit Swiftyedit.

## How do I fix CVE-2023-47350?

Upgrade swiftyedit/swiftyedit to 1.2.0 or later.

## Is CVE-2023-47350 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-47350 and fix it if it is affected.

What it is: CVE-2023-47350 is a high-severity vulnerability in n/a, published on 22 Nov 2023. 
Exploitation: There is no known exploitation of CVE-2023-47350 in the wild and no public exploit code.

Affected packages and fixed versions:
- swiftyedit/swiftyedit (Packagist): affected all versions; fixed in 1.2.0
- swiftyedit/swiftyedit (Packagist): affected all versions; fixed in 1.2.0

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-2023-47350/ (Markdown: https://insights.sbomify.com/CVE-2023-47350/index.md)
```

## Sources

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

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