dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-54239

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 dugudlabs Eyewear prescription form eyewear-prescription-form allows Privilege Escalation.This issue affects Eyewear prescription form: from n/a through <= 4.0.18.

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

A missing authorization vulnerability in the dugudlabs Eyewear prescription form WordPress plugin (eyewear-prescription-form) allows authenticated users to perform actions beyond their intended privilege level, leading to privilege escalation. The plugin fails to properly validate user capabilities before executing sensitive functions in version 4.0.18 and below.

MitigationUpdate the eyewear-prescription-form plugin to the latest version available from the vendor, which should contain proper authorization checks. If no update is available, disable the plugin and review all admin-capable users in the WordPress installation.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate the plugin installation directory
    Check your WordPress plugins folder (wp-content/plugins/) for a directory named 'eyewear-prescription-form' or search for files containing 'eyewear' in the plugins directory using: find /path/to/wp-content/plugins -type d -name '*eyewear*'
    Affected if The plugin directory exists on the server
  2. Determine the installed plugin version
    Open the main plugin PHP file (typically eyewear-prescription-form.php) and locate the 'Version:' header comment in the file docblock, or check the plugin's readme.txt file for the version number
    Affected if The reported version is 4.0.18 or lower (e.g., 4.0.18, 4.0.17, 4.0.10, etc.)
  3. Verify if the plugin is currently active
    Log into WordPress admin panel and navigate to Plugins > Installed Plugins, or query the WordPress options table: SELECT * FROM wp_options WHERE option_name = 'active_plugins'; and check if 'eyewear-prescription-form/eyewear-prescription-form.php' appears in the serialized array
    Affected if The plugin appears in the active_plugins list and is enabled
  4. Identify users with low-level privileges
    In WordPress admin, go to Users > All Users and review roles, or query: SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities'; to see which users have only 'subscriber', 'contributor', or 'author' roles
    Affected if There are users with roles below Administrator who have authenticated access to the site (potential privilege escalation targets)
  5. Inspect plugin for capability checks
    Examine the main plugin PHP file for function calls that handle sensitive operations (e.g., save, update, delete, admin actions) and verify if each is preceded by a capability check like 'current_user_can()' or 'wp_verify_nonce()'. Search for patterns such as 'add_action' or 'add_shortcode' handling form submissions without capability verification
    Affected if Sensitive functions lack proper current_user_can() checks or nonce verification, indicating the authorization flaw is present

You are affected if the eyewear-prescription-form plugin is installed at version 4.0.18 or below and is currently active, allowing any authenticated user to potentially escalate privileges through unchecked sensitive functions.

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

Update the eyewear-prescription-form plugin to the latest version available from the vendor, which should contain proper authorization checks. If no update is available, disable the plugin and review all admin-capable users in the WordPress installation.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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