# CVE-2026-16058: YayCurrency < 3.3.5 - Unauthenticated Order and Vendor Financial Data Disclosure via Dokan Integration

> Unauthenticated attackers can read sensitive order totals and vendor financial data by iterating identifiers due to missing capability checks in the YayCurrency plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-gw8v-vjq2-rf32

## What is CVE-2026-16058?

CVE-2026-16058 is a medium-severity missing authorization vulnerability in Unknown YayCurrency, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-16058?


## How do I fix CVE-2026-16058?

No fix has been published for CVE-2026-16058 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-16058 being exploited?

There is no known exploitation of CVE-2026-16058 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16058 and fix it if it is affected.

What it is: CVE-2026-16058 is a medium-severity missing authorization vulnerability in Unknown YayCurrency, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-16058 in the wild and no public exploit code.

Affected product: Unknown YayCurrency. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16058/ (Markdown: https://insights.sbomify.com/CVE-2026-16058/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16058
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16058
- OSV: https://osv.dev/vulnerability/CVE-2026-16058

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16058/
Summaries are generated and may contain mistakes; the official description above is the record.