CVE-2026-16058

Deferred Deferred - Pending Action

Unauthenticated Access to Vendor Financial Data in YayCurrency WordPress Plugin

Publication date: 2026-08-19

Last updated on: 2026-08-26

Assigner: WPScan

Description

The YayCurrency WordPress plugin before 3.3.5 does not perform any capability or ownership check on several of its multi-vendor integration handlers that are reachable by unauthenticated users, allowing anyone to read the store's order totals and its vendors' earnings, balance ledgers, and withdrawal histories by iterating identifiers.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-19

Last Modified

2026-08-26

Generated

2026-09-08

AI Q&A

2026-08-19

EPSS Evaluated

2026-09-07

NVD

CVE-2026-16058

EUVD

EUVD-2026-62269

Affected Vendors & Products

Vendor	Product	Version / Range
yaycurrency	yaycurrency	to 3.3.5 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-639	The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

Executive Summary

The YayCurrency WordPress plugin before version 3.3.5 has an unauthenticated access vulnerability due to missing capability or ownership checks in its multi-vendor integration handlers. This allows anyone to access sensitive financial data by iterating through identifiers.

Detection Guidance

Check if the YayCurrency plugin version is below 3.3.5 by inspecting the WordPress admin panel or using commands like 'wp plugin list' in WP-CLI. Look for unauthenticated access to endpoints handling financial data by monitoring network traffic or logs for requests to multi-vendor integration handlers.

Impact Analysis

Unauthenticated users can read store order totals, vendor earnings, balance ledgers, and withdrawal histories. This exposes sensitive financial information and violates data confidentiality.

Compliance Impact

This vulnerability likely violates GDPR and HIPAA due to unauthorized access to financial data. GDPR requires protecting personal data, while HIPAA mandates securing protected health information. Non-compliance risks legal penalties.

Mitigation Strategies

Update the YayCurrency plugin to version 3.3.5 or later immediately. If updating is not possible, disable the plugin temporarily until a patch is applied. Review server logs for signs of exploitation and restrict access to sensitive endpoints.

Hi! I’m here to help you understand CVE-2026-16058. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70