dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-3277

MEDIUM · 5.0 CVSS v3.1 Published 2024-05-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Yumpu ePaper WordPress plugin lacks capability checks on its ajax_handler function, allowing any authenticated user with subscriber-level privileges to upload and publish PDFs and modify the plugin's API key. This is a Broken Access Control vulnerability where low-privilege users can perform administrative actions.

MitigationUpdate the Yumpu ePaper plugin to version 2.0.25 or later which implements proper capability checks on the ajax_handler function. Additionally, audit existing user accounts and revoke any unauthorized PDF publications or API key changes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Yumpu ePaper plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Yumpu ePaper' in the installed plugins list, or query the wp_options table for the plugin active state
    Affected if The plugin appears in the WordPress installation and is active
  2. Check the installed plugin version
    In WordPress admin > Plugins > Yumpu ePaper, view the plugin details to see the version number, or query the wp_options table for the plugin version entry
    Affected if The installed version is lower than 2.0.25
  3. Audit user accounts with subscriber-level access
    Navigate to WordPress admin > Users and review all accounts assigned the Subscriber role; check if any were created recently or have elevated activity
    Affected if There are subscriber accounts that exist beyond expected legitimate users, or subscriber accounts with modified capabilities
  4. Inspect for unauthorized PDF publications
    Query the wp_posts table for posts of type 'yumpu' or review the plugin's PDF content library in the admin panel; check for publications created by low-privilege users
    Affected if PDF publications exist that were created or modified by users without administrator privileges
  5. Review plugin API key configuration for unauthorized changes
    Check the plugin settings page in WordPress admin under Yumpu ePaper settings, or query the wp_options table for yumpu_api_key and related configuration entries; verify the API key matches expected values
    Affected if The stored API key differs from the organization's known valid key, or settings were modified by non-admin users

A user is affected if the Yumpu ePaper plugin is installed with a version lower than 2.0.25, or if any low-privilege users have modified plugin settings or published content without admin oversight.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Yumpu ePaper plugin to version 2.0.25 or later which implements proper capability checks on the ajax_handler function. Additionally, audit existing user accounts and revoke any unauthorized PDF publications or API key changes.

Recommended fix Moderate confidence

2.0.25 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the Yumpu ePaper publishing plugin
  4. 4. Check if an update is available for the plugin
  5. 5. If an update is available, click to update the plugin to the latest version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3277 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-3277 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data