dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-11724

HIGH · 8.8 CVSS v3.1 Published 2025-11-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 EM Beer Manager plugin for WordPress is vulnerable to arbitrary file upload leading to remote code execution in all versions up to, and including, 3.2.3. This is due to missing file type validation in the EMBM_Admin_Untappd_Import_image() function and missing authorization checks on the wp_ajax_embm-untappd-import action. This makes it possible for authenticated attackers, with subscriber-level access and above, to upload arbitrary files including PHP files and execute code on the server granted they can provide a mock HTTP server that responds with specific JSON data.

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 EM Beer Manager WordPress plugin up to version 3.2.3 has an arbitrary file upload vulnerability in the EMBM_Admin_Untappd_Import_image() function. The AJAX action 'wp_ajax_embm-untappd-import' lacks proper authorization checks, allowing any authenticated user with subscriber-level access to upload arbitrary files including PHP scripts. Combined with missing file type validation, this enables remote code execution.

MitigationUpgrade to version 3.2.4 or later. In the interim, disable the plugin or restrict access to the embm-untappd-import AJAX endpoint via server-side rules. The fix requires adding capability checks (require manage_options or similar) and implementing strict file type validation with whitelist extension and MIME type verification before any file write operations.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check EM Beer Manager plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find EM Beer Manager. Compare the version number to the affected range (3.2.3 or earlier).
    Affected if Installed version is 3.2.3 or lower
  2. Verify the vulnerable AJAX endpoint is exposed
    Check if the AJAX action 'embm-untappd-import' is registered by searching the plugin files for 'wp_ajax_embm-untappd-import' or by inspecting the site's AJAX handler at /wp-admin/admin-ajax.php?action=embm-untappd-import.
    Affected if The AJAX endpoint is registered and responds to requests
  3. Confirm any subscriber-level user exists
    In WordPress admin, go to Users and review user roles. Verify if any user has the Subscriber role (or any role below Editor).
    Affected if At least one user with Subscriber role or lower privilege exists on the site
  4. Inspect the untappd import function for missing validation
    Locate the EMBM_Admin_Untappd_Import_image function in the plugin files (typically in includes/admin or similar directory). Examine the code for capability checks (like 'manage_options') and file type validation (extension and MIME type whitelists).
    Affected if The function lacks capability checks AND does not validate file extensions/MIME types before saving files

A user is affected if the plugin version is 3.2.3 or earlier, the embm-untappd-import AJAX endpoint is active, and any subscriber-level user account exists on the site.

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

Upgrade to version 3.2.4 or later. In the interim, disable the plugin or restrict access to the embm-untappd-import AJAX endpoint via server-side rules. The fix requires adding capability checks (require manage_options or similar) and implementing strict file type validation with whitelist extension and MIME type verification before any file write operations.

Recommended fix High confidence

EM Beer Manager version 3.2.4

  1. 1. Log in to the WordPress admin dashboard with administrator access
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'EM Beer Manager' in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to the latest patched version
  5. 5. Alternatively, download the updated plugin version from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is functioning correctly and test that the untappd import functionality still works as expected

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11724 — 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-2025-11724 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