CVE-2025-14366
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 · uneditedThe 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 authorization checks on the SubmitCatProductRequest AJAX action. This makes it possible for unauthenticated attackers to create arbitrary WooCommerce products with custom names, prices, and category assignments via the 'Name', 'Price', and 'Parent' parameters.
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 confidenceThe Eyewear prescription form WordPress plugin lacks authorization checks on the SubmitCatProductRequest AJAX action, allowing unauthenticated attackers to create arbitrary WooCommerce products with custom names, prices, and category assignments. This is a broken access control vulnerability where the AJAX endpoint accepts requests from any user without verifying permissions.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify the Eyewear prescription form plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Eyewear prescription form' or check the wp-content/plugins directory for an eyewear-related plugin folderAffected if Plugin is present in the installation
-
Confirm WooCommerce is activeCheck that WooCommerce plugin is installed and active, as the vulnerability creates WooCommerce productsAffected if WooCommerce is active and the Eyewear plugin is installed
-
Identify the vulnerable AJAX endpointSearch plugin code for 'SubmitCatProductRequest' action hook (typically add_action('wp_ajax_nopriv_SubmitCatProductRequest' or 'wp_ajax_SubmitCatProductRequest')Affected if The AJAX action 'SubmitCatProductRequest' is registered in the plugin
-
Test unauthenticated access to the AJAX endpointSend a POST request to /wp-admin/admin-ajax.php with action=SubmitCatProductRequest and test parameters (name, price, category) without providing any authentication cookies or nonceAffected if The server accepts and processes the request without requiring authentication (no 403 or login redirect)
-
Inspect the AJAX handler for capability checksLocate the callback function for SubmitCatProductRequest and verify it calls current_user_can() or similar capability check before creating productsAffected if The handler lacks a current_user_can() check or performs no authorization verification
If the Eyewear prescription form plugin is installed with WooCommerce and the SubmitCatProductRequest AJAX endpoint responds to unauthenticated requests without verifying user capabilities, the environment is affected by CVE-2025-14366.
Generated from the published advisory. Verify against your own configuration.
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 dataAdd a capability check (e.g., current_user_can('manage_options')) and nonce verification to the SubmitCatProductRequest AJAX handler to ensure only authorized users can create products.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14366 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-14366 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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