Quick answers
- Is CVE-2026-125844 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-125844 being exploited in the wild.
- How severe is CVE-2026-125844?
- High severity, with a CVSS score of 8.8, published 11 November 2026.
- Which products and versions are affected?
- WordPress.org Vice through 1.4.
- Is there a fix for CVE-2026-125844?
- No fixed version is recorded yet. Remove and replace the affected theme with an actively maintained alternative. Deactivating the theme alone does not mitigate the vulnerability; the theme must be completely removed from the WordPress installation. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-125844 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-125844?
- Check whether you run WordPress.org Vice 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
Remove and replace the affected theme with an actively maintained alternative. Deactivating the theme alone does not mitigate the vulnerability; the theme must be completely removed from the WordPress installation.
Technical details
The vice WordPress theme through version 1.4 lacks proper CSRF token validation on sensitive operations. Exploitation requires an authenticated user to click a malicious link or visit a crafted page controlled by an attacker. The vulnerability allows state-changing actions to be performed on behalf of the logged-in user without their explicit consent. No official patch is available from the theme developer.
Affected products
- WordPress.org vice through 1.4
Timeline
- 2026-10-10: disclosed
- 2026-11-11: advisory