# CVE-2024-4475: WP Logs Book <= 1.0.1 - Log Clearing via CSRF

> Attackers can force logged-in admins to clear logs via CSRF, compromising audit trails in the WP Logs Book plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-623w-rmj9-c99m

## What is CVE-2024-4475?

CVE-2024-4475 is a medium-severity vulnerability in Unknown WP Logs Book, published on 21 Jun 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The WP Logs Book WordPress plugin through 1.0.1 does not have CSRF check when clearing logs, which could allow attackers to make a logged in admin clear the logs them via a CSRF attack

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

## Which versions are affected by CVE-2024-4475?

It affects 1 product.


Products: Onetarek Wp Logs Book.

## How do I fix CVE-2024-4475?

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

## Is CVE-2024-4475 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4475 exists.

## Other vulnerabilities in Unknown WP Logs Book

- [CVE-2024-4474](https://insights.sbomify.com/CVE-2024-4474/): WP Logs Book <= 1.0.1 - Disable Logging via CSRF (medium 4.3)
- [CVE-2024-4477](https://insights.sbomify.com/CVE-2024-4477/): WP Logs Book <= 1.0.1 - Unauthenticated Stored XSS (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-4475 and fix it if it is affected.

What it is: CVE-2024-4475 is a medium-severity vulnerability in Unknown WP Logs Book, published on 21 Jun 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4475 exists.

Affected product: Unknown WP Logs Book. 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-2024-4475/ (Markdown: https://insights.sbomify.com/CVE-2024-4475/index.md)
```

## Sources

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

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