dbcve.org
EmbedpressWordPress extension · Wpdeveloper

CVE-2024-31274

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-09
Fix available
A fix is available. Upgrade to 3.9.12 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Missing Authorization vulnerability in WPDeveloper EmbedPress.This issue affects EmbedPress: from n/a through 3.9.11.

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 · moderate confidence

This is a missing authorization vulnerability in the EmbedPress WordPress plugin. The issue allows unauthenticated or unauthorized users to access functionality that should require proper authentication or capability checks. The vulnerability affects versions up to and including 3.9.11.

MitigationUpdate EmbedPress to the latest version available from the WordPress plugin repository to obtain the patched release that addresses this authorization flaw.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EmbedpressWordPress extension
Affected:< 3.9.12

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Check if EmbedPress plugin is installed
    Navigate to WordPress Admin > Plugins > Installed Plugins. Look for 'EmbedPress' in the list. Alternatively, check for the presence of the /wp-content/plugins/embedpress/ directory on the server.
    Affected if The plugin is installed and active
  2. Determine installed EmbedPress version
    In WordPress Admin > Plugins, find EmbedPress and view the version number displayed below the plugin name. Alternatively, inspect /wp-content/plugins/embedpress/readme.txt or the plugin header in /wp-content/plugins/embedpress/embedpress.php to find the 'Version' field.
    Affected if The version is less than 3.9.12 (including 3.9.11 and earlier)
  3. Verify plugin is active on the site
    In WordPress Admin > Plugins, confirm that EmbedPress shows as 'Active' rather than 'Inactive' or 'Must Use'. Check the site's frontend to see if any EmbedPress functionality (embedded content from providers like YouTube, Vimeo, Google Docs) is in use.
    Affected if The plugin is active and in use on the site
  4. Check for unauthorized access to plugin features
    Test whether unauthenticated users can access functionality that should require authentication. This may include REST API endpoints under /wp-json/embedpress/ or similar paths. Use a browser in incognito mode or curl to make requests without authentication cookies.
    Affected if Unauthenticated or lower-privileged users can access content or perform actions that should require higher privileges

You are affected if EmbedPress version is less than 3.9.12 AND the plugin is active on your WordPress site, as this version range contains the missing authorization vulnerability.

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
Upgrade available Upgrade to 3.9.12 or later
Fixed in 3.9.12
Interim mitigation

Update EmbedPress to the latest version available from the WordPress plugin repository to obtain the patched release that addresses this authorization flaw.

Recommended fix High confidence

EmbedPress 3.9.12

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find EmbedPress in the plugin list
  4. Click 'Update now' if an update is available, or click 'Delete' and reinstall version 3.9.12
  5. Verify the plugin version is 3.9.12 after updating
  6. Test that the authorization controls are functioning properly

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

Fix this in Embedpress Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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