xtemos WoodMart Plugin up to 8.3.9 on WordPress information expsure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in xtemos WoodMart Plugin up to 8.3.9 on WordPress. The impacted element is an unknown function. Performing a manipulation results in information expsure. This vulnerability is reported as CVE-2026-32405. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in xtemos WoodMart Plugin up to 8.3.9 on WordPress. It has been classified as problematic. This affects an unknown code. The manipulation with an unknown input leads to a information expsure vulnerability. CWE is classifying the issue as CWE-497. The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does. This is going to have an impact on confidentiality. The summary by CVE is:
Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in xtemos WoodMart woodmart allows Retrieve Embedded Sensitive Data.This issue affects WoodMart: from n/a through <= 8.3.9.
The weakness was disclosed by Phat Rio. It is possible to read the advisory at patchstack.com. This vulnerability is uniquely identified as CVE-2026-32405 since 03/12/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-11922). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.7
VulDB Base Score: 4.3
VulDB Temp Score: 4.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
ADP CISA Base Score: 5.3
ADP CISA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Information expsureCWE: CWE-497
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
03/12/2026 CVE reserved03/13/2026 Advisory disclosed
03/13/2026 VulDB entry created
03/20/2026 VulDB entry last update
Sources
Advisory: patchstack.comResearcher: Phat Rio
Status: Not defined
CVE: CVE-2026-32405 (🔒)
GCVE (CVE): GCVE-0-2026-32405
GCVE (VulDB): GCVE-100-350907
EUVD: 🔒
Entry
Created: 03/13/2026 13:49Updated: 03/20/2026 20:28
Changes: 03/13/2026 13:49 (54), 03/15/2026 00:13 (1), 03/20/2026 20:28 (12)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.