dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14365

MEDIUM · 5.3 CVSS v3.1 Published 2025-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 →
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
The Eyewear prescription form plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 6.0.1. This is due to missing capability checks on the RemoveItems AJAX action. This makes it possible for unauthenticated attackers to delete arbitrary WooCommerce product categories, including all of their child categories, via the 'catIds' parameter.

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 Eyewear WordPress plugin lacks capability checks on its RemoveItems AJAX action, allowing unauthenticated users to delete any WooCommerce product category by submitting category IDs via the 'catIds' parameter. This is a missing function level access control vulnerability affecting versions up to 6.0.1.

MitigationUpdate to version 6.0.2 or later which implements proper authorization checks on the RemoveItems AJAX action. Until patched, consider disabling the plugin or blocking the specific AJAX endpoint at the web server level.

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 Eyewear plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and find the Eyewear plugin. Check the version number listed under the plugin name, or inspect the plugin header in /wp-content/plugins/eyewear/eyewear.php
    Affected if The installed version is 6.0.1 or earlier
  2. Confirm WooCommerce is active
    In WordPress admin, verify WooCommerce is installed and active under Plugins > Installed Plugins. The vulnerability targets WooCommerce product categories, so WooCommerce must be present.
    Affected if WooCommerce is active and the Eyewear plugin version is 6.0.1 or earlier
  3. Test unauthenticated AJAX endpoint access
    Send a POST request to /wp-admin/admin-ajax.php with action=RemoveItems and a catIds parameter containing a category ID (e.g., curl -X POST http://target/wp-admin/admin-ajax.php -d 'action=RemoveItems&catIds=1'). No authentication should be required for the vulnerability to exist.
    Affected if The request returns a successful response without requiring login credentials (status 200 and no auth error)
  4. Compare version to affected range
    Review the detected version against the affected range: versions up to and including 6.0.1 are vulnerable. Versions 6.0.2 and later contain the fix.
    Affected if The installed version is 6.0.1 or earlier and the AJAX endpoint responds without authentication

A user is affected if the Eyewear plugin version is 6.0.1 or earlier, WooCommerce is active, and the RemoveItems AJAX action is accessible without authentication.

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 to version 6.0.2 or later which implements proper authorization checks on the RemoveItems AJAX action. Until patched, consider disabling the plugin or blocking the specific AJAX endpoint at the web server level.

Recommended fix High confidence

6.0.2 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Eyewear plugin
  4. Check if an update to version 6.0.2 or later is available
  5. If update available, click 'Update Now' to install the fixed version
  6. If no update shown, manually download the latest version from WordPress.org plugins repository and upload via Plugins > Add New > Upload Plugin
  7. Verify the update was successful by checking the plugin version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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