# CVE-2024-1375: Event post <= 5.9.10 - Cross-Site Request Forgery

> Unauthenticated attackers can modify post metadata by tricking logged-in users into clicking a link due to missing nonce checks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Jul 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-2wpm-fgjv-c368

## What is CVE-2024-1375?

CVE-2024-1375 is a medium-severity vulnerability in bastho Event post, published on 12 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Event post plugin for WordPress is vulnerable to unauthorized bulk metadata update due to a missing nonce check on the save_bulkdatas function in all versions up to, and including, 5.9.10. This makes it possible for unauthenticated attackers to update post_meta_data via a forged request, granted they can trick a logged-in user into performing an action such as clicking on a link.

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

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


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

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

## Is CVE-2024-1375 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1375 is a medium-severity vulnerability in bastho Event post, published on 12 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-1375 in the wild and no public exploit code.

Affected product: bastho Event post. 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-1375/ (Markdown: https://insights.sbomify.com/CVE-2024-1375/index.md)
```

## Sources

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

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