Blog

"Prevention is cheaper than a breach"

Home / Threats / CVE-2026-19613

CVE-2026-19613 - Before 4 Plugin

CVE-2026-19613

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.

CVE-2026-19613

UNKNOWN CVSS 0.0 Published 2026-08-16 Updated 2026-08-16
AI Risk Low (8/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P5 Monitor
Severity Band UNKNOWN
CVSS Vector Unspecified
Affected Components 2
Reference Links 1
AI Risk Engine Low (8/100)
Exploitability High
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-08-16 CVE published and first recorded in the threat feed.
  2. 2026-08-16 Record updated with latest vulnerability metadata.
  3. 2026-08-16 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 1 day ago

AI enriched 1 day ago (2026-08-16 17:43 UTC)

Technical Summary

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.

Potential Impact

Severity is UNKNOWN (CVSS 0.0). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on remote code execution potential.

Primary risk drivers: remote code execution potential

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 8/100 (Low, High) with priority P5 Monitor. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Before 4 PLUGIN · before-4 Affected: < 4.3.10 Fixed in: 4.3.10
Ecs PLUGIN · ecs Affected: < 4.3.10 Fixed in: 4.3.10
Scroll to top