Quick answers
- Is CVE-2026-93927 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93927 being exploited in the wild.
- How severe is CVE-2026-93927?
- Critical severity, with a CVSS score of 9.8, published 10 October 2026.
- Which products and versions are affected?
- Axiomthemes Veto up to 1.6.0.
- Is there a fix for CVE-2026-93927?
- No fixed version is recorded yet. Apply a Patchstack mitigation rule to block attack attempts until an official patch becomes available. Consider disabling or removing the Veto theme if an update is not available from your hosting provider or web developer. 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-93927 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-93927?
- Check whether you run Axiomthemes Veto 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
Apply a Patchstack mitigation rule to block attack attempts until an official patch becomes available. Consider disabling or removing the Veto theme if an update is not available from your hosting provider or web developer.
Technical details
This is a deserialization of untrusted data vulnerability (CWE-502) leading to PHP object injection in the Veto WordPress theme. An unauthenticated attacker can exploit this by sending specially crafted data that causes the server to instantiate malicious objects, leading to remote code execution. No official patch has been released as of the advisory date.
Affected products
- Axiomthemes Veto up to 1.6.0
Timeline
- 2026-10-10: disclosed
- 2026-02-28: other: Reported to Patchstack