CVE-2026-6932 json
Woo Commerce Minimum Weight <= 3.0.1 - Cross-Site Request Forgery via Settings Update Form
published 5mo ago modified 4mo ago also EUVD-2026-29412
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
The Woo Commerce Minimum Weight plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 3.0.1. This is due to missing nonce verification on the settings update handler in edit-weight.php. This makes it possible for unauthenticated attackers to modify the minimum order weight setting by tricking a site administrator into clicking a link or visiting an attacker-controlled page containing a forged POST request.
Is CVE-2026-6932 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5mo ago
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
Affected products
- hemant29 Woo Commerce Minimum Weight
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/b2c44c95-6a00-4c56-967b-003ce307f90c?source=cve
- plugins.trac.wordpress.org /browser/woo-commerce-min-weight/trunk/edit-weight.php#L5
- plugins.trac.wordpress.org /browser/woo-commerce-min-weight/tags/3.0.1/edit-weight.php#L5
- plugins.trac.wordpress.org /browser/woo-commerce-min-weight/trunk/edit-weight.php#L3
- plugins.trac.wordpress.org /browser/woo-commerce-min-weight/tags/3.0.1/edit-weight.php#L3
Sources
- CVE List CVE-2026-6932
- NVD CVE-2026-6932
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.