Quick answers
- Is CVE-2026-112219 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112219 being exploited in the wild.
- How severe is CVE-2026-112219?
- Informational severity, published 23 October 2026.
- Which products and versions are affected?
- WordPress.org Download Monitor before 5.3.5.
- Is there a fix for CVE-2026-112219?
- Yes: fixed in 5.3.5. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-112219 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-112219?
- Check whether you run WordPress.org Download Monitor at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 5.3.5
Technical details
This is an incorrect authorization vulnerability (CWE-863) in the Download Monitor REST endpoint that manages approved filesystem paths. A subsite administrator on a multisite installation can bypass restrictions intended for network administrators and approve arbitrary filesystem locations, allowing the plugin to serve readable files outside the uploads directory—including files from other subsites—to unauthenticated visitors. The vulnerability requires the attacker to be a trusted subsite administrator on a multisite installation.
Affected products
- WordPress.org Download Monitor before 5.3.5
Timeline
- 2026-10-21: disclosed
- 2026-10-23: advisory: Published on NVD