dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-37276

MEDIUM · 5.3 CVSS v3.1 Published 2024-11-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 fifu.App Featured Image from URL allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Featured Image from URL: from n/a through 4.8.1.

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 broken access control vulnerability in the Featured Image from URL WordPress plugin where the application fails to properly authorize users before allowing access to certain functionality or data. An attacker with minimal privileges (or potentially unauthenticated) can exploit incorrectly configured access control security levels to perform actions or access resources they should not be permitted to access.

MitigationImplement proper authorization checks (capability checks, nonce verification, and role-based access control) on all sensitive functions and AJAX endpoints in the plugin, following WordPress best practices for security.

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
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. Verify the Featured Image from URL plugin is installed and active
    Navigate to WordPress admin > Plugins and confirm the plugin 'Featured Image from URL' appears in the active plugins list
    Affected if The plugin is installed and activated in WordPress
  2. Check the installed plugin version
    In the Plugins list, locate the plugin and view the version number under the plugin name. Compare this to any version referenced in security advisories for this CVE
    Affected if The installed version matches or falls within the affected version range (if disclosed)
  3. Inspect AJAX endpoints for missing capability checks
    Examine the plugin PHP files for AJAX handlers (wp_ajax_ and wp_ajax_nopriv_ hooks). Check if these endpoints include current_user_can() or similar authorization checks before executing sensitive operations
    Affected if AJAX endpoints lack capability checks and are accessible to low-privilege or unauthenticated users (wp_ajax_nopriv_ hooks present without proper authorization)
  4. Verify nonce verification on sensitive functions
    Review the plugin code for functions that modify settings, create posts, or access data. Confirm that wp_verify_nonce() or check_admin_referer() is called before executing these operations
    Affected if Sensitive functions lack nonce verification, allowing CSRF attacks
  5. Check role-based access control configuration
    Review the plugin settings page and code to identify which user roles (Subscriber, Contributor, Author, Editor) can access plugin features. Test by creating a low-privilege test user and attempting to access plugin functionality
    Affected if Low-privilege users (such as Subscribers) can perform actions reserved for Administrators

You are affected if the Featured Image from URL plugin is active AND its version falls within the affected range AND sensitive AJAX endpoints are accessible to unauthenticated or low-privilege users without proper capability or nonce verification.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks (capability checks, nonce verification, and role-based access control) on all sensitive functions and AJAX endpoints in the plugin, following WordPress best practices for security.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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