# CVE-2026-19613: ECS < 4.3.10 - Contributor+ Arbitrary Post Meta Disclosure via Dynamic Repeater ACF Source

> Contributor-level users can read private or draft post metadata and custom fields from posts they do not own via the ECS plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-4p53-g645-qhr2

## What is CVE-2026-19613?

CVE-2026-19613 is a medium-severity vulnerability in Unknown ECS, published on 16 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The ECS  WordPress plugin before 4.3.10 does not perform ownership or post-status checks when one of its dynamic repeater data sources reads custom field values from a user-supplied post identifier, allowing users with a contributor-level account or above to read custom field values and post metadata from posts they do not own, including private and draft ones.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-19613 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19613 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19613 is a medium-severity vulnerability in Unknown ECS, published on 16 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19613 exists.

Affected product: Unknown ECS. 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-19613/ (Markdown: https://insights.sbomify.com/CVE-2026-19613/index.md)
```

## Sources

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

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