# CVE-2024-3277: Yumpu ePaper publishing <= 2.0.24 - Missing Authorization to PDF Upload, Publishing, and API Key Modification

> Authenticated subscribers can upload and publish PDFs and modify API keys due to missing capability checks in the Yumpu ePaper WordPress plugin.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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:** Not needed
- **Fix available:** No
- **Published:** 30 May 2024
- **Updated:** 8 Apr 2026

## What is CVE-2024-3277?

CVE-2024-3277 is a medium-severity missing authorization vulnerability in Yumpu E-Paper publishing, published on 30 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Yumpu ePaper publishing plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the ajax_handler function in all versions up to, and including, 2.0.24. This makes it possible for authenticated attackers, with subscriber-level access and above, to upload PDF files and publish them, as well as modify the API key.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2024-3277 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3277 is a medium-severity missing authorization vulnerability in Yumpu E-Paper publishing, published on 30 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-3277 in the wild and no public exploit code.

Affected product: Yumpu E-Paper publishing. 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-3277/ (Markdown: https://insights.sbomify.com/CVE-2024-3277/index.md)
```

## Sources

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

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