cve.bz

CVE-2026-92408 WPS Bookings for WooCommerce < 3.13.1 - Unauthenticated Price Manipulation via booking_price

5.3 mediumEPSS 0.3%

Medium (5.3) in unknown wps bookings for woocommerce. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
The WPS Bookings for WooCommerce WordPress plugin before 3.13.1 does not validate a price value taken from user input before using it to set the product price, allowing unauthenticated users to purchase bookable services at a price of their choosing, including zero.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 17th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-472 External Control of Assumed-Immutable Web Parameter
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
Assigned by
WPScan (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-92408 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-92408?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-92408?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-92408 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-92408

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-92408](https://cve.bz/cve/badge/CVE-2026-92408.svg)](https://cve.bz/cve/CVE-2026-92408)

HTML:

<a href="https://cve.bz/cve/CVE-2026-92408"><img src="https://cve.bz/cve/badge/CVE-2026-92408.svg" alt="CVE-2026-92408"></a>

Affected

  • unknown:wps bookings for woocommerce

Attack patterns (CAPEC)

  • CAPEC-31 Accessing/Intercepting/Modifying HTTP Cookies Likelihood: High · Severity: High
  • CAPEC-39 Manipulating Opaque Client-based Data Tokens Likelihood: High · Severity: Medium
  • CAPEC-146 XML Schema Poisoning Likelihood: Low · Severity: High
  • CAPEC-226 Session Credential Falsification through Manipulation Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON