Quick answers
- Is CVE-2026-111829 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111829 being exploited in the wild.
- How severe is CVE-2026-111829?
- Medium severity, with a CVSS score of 6.5, published 19 October 2026.
- Which products and versions are affected?
- WP Mailster through 1.9.1.0.
- Is there a fix for CVE-2026-111829?
- Yes: fixed in 1.9.2.0. Until then: Update to version 1.9.2.0 or later. If an immediate update is not possible, restrict contributor-level access to trusted users only. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111829 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-111829?
- Check whether you run WP Mailster 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: 1.9.2.0
Update to version 1.9.2.0 or later. If an immediate update is not possible, restrict contributor-level access to trusted users only.
Technical details
The plugin improperly controls filenames in include/require statements, enabling local file inclusion (LFI) attacks. This requires contributor-level privileges to exploit. Successful exploitation allows an attacker to read arbitrary files from the server filesystem, which may contain sensitive data such as database credentials or configuration files that could lead to further compromise.
Affected products
- WP Mailster WP Mailster through 1.9.1.0
Timeline
- 2026-10-06: disclosed
- 2026-10-19: advisory