# CVE-2022-45393: Cross-Site Request Forgery in Jenkins Delete log Plugin

> Attackers can delete build logs via CSRF in the Jenkins Delete log Plugin, requiring an upgrade to mitigate.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Nov 2022
- **Updated:** 30 Apr 2025
- **Also known as:** GHSA-hw4f-g7wh-xp52

## What is CVE-2022-45393?

CVE-2022-45393 is a low-severity vulnerability in Jenkins Delete log Plugin, published on 15 Nov 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A cross-site request forgery (CSRF) vulnerability in Jenkins Delete log Plugin 1.0 and earlier allows attackers to delete build logs.

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

## Which versions are affected by CVE-2022-45393?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:delete-log-plugin. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:delete-log-plugin` | Maven | All versions to 1.0 | None |
| `org.jenkins-ci.plugins:delete-log-plugin` | Maven | All versions to 1.0 | None |

Products: Jenkins Delete Log.

## How do I fix CVE-2022-45393?

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

## Is CVE-2022-45393 being exploited?

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

## Other vulnerabilities in Jenkins Delete log Plugin

- [CVE-2022-45394](https://insights.sbomify.com/CVE-2022-45394/): Missing permission check in Jenkins Delete log Plugin (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-45393 and fix it if it is affected.

What it is: CVE-2022-45393 is a low-severity vulnerability in Jenkins Delete log Plugin, published on 15 Nov 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-45393 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:delete-log-plugin (Maven): affected all versions up to 1.0; no fix listed
- org.jenkins-ci.plugins:delete-log-plugin (Maven): affected all versions up to 1.0; no fix listed

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

## Sources

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

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