What is the CVSS score of CVE-2026-65581?

CVE-2026-65581 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.3%.

Which versions of AI ANN are affected by CVE-2026-65581?

The AI ANN WordPress theme (AxiomThemes) versions through 1.29.0 contain a critical PHP Object Injection vulnerability (CVE-2026-65581) exploitable by unauthenticated remote attackers to execute…

How to fix or mitigate CVE-2026-65581?

Within 24 hours, identify all WordPress installations using AI ANN theme versions ≤1.29.0 and immediately disable the theme or take sites offline; simultaneously deploy WAF rules to block malicious serialized PHP object payloads targeting the vulnerability. Within 7 days, implement dedicated monitoring and alerting for exploitation attempts in web server and WAF logs, and escalate to AxiomThemes for emergency patch status and timeline. Within 30 days, execute a complete migration to an actively maintained, security-patched WordPress theme, prioritizing sites handling customer data, with full regression testing before returning to production.

AI ANN CVE-2026-65581

EUVD-2026-53879 CRITICAL

Deserialization of Untrusted Data (CWE-502)

2026-08-06 Patchstack

GHSA-xqx7-fh5p-977f

PHP WordPress Deserialization Ai Ann Wordpress Theme Axiomthemes

9.8

CVSS 3.1 · Vendor: Patchstack

Severity by source

Vendor (Patchstack) PRIMARY

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

vuln.today AI

9.8 CRITICAL

Unauthenticated network-reachable deserialization sink (AV:N/AC:L/PR:N/UI:N) that, with a viable POP chain, yields full C/I/A compromise; scope unchanged as impact stays on the host.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Aug 06, 2026 - 15:45 vuln.today

CVE Published

Aug 06, 2026 - 14:27 cve.org

CRITICAL 9.8

DescriptionCVE.org

Unauthenticated PHP Object Injection in AI ANN <= 1.29.0 versions.

AnalysisAI

PHP Object Injection in the AI ANN WordPress theme (by AxiomThemes) affects all versions up to and including 1.29.0, allowing unauthenticated remote attackers to inject crafted serialized PHP objects that are deserialized by the theme. When a suitable POP (property-oriented programming) gadget chain is present in the theme, WordPress core, or an active plugin, this can escalate to remote code execution, arbitrary file operations, or data compromise. Reported by Patchstack; no public exploit identified at time of analysis, though the CVSS 9.8 rating reflects the unauthenticated, network-reachable nature of the flaw.

Technical ContextAI

The vulnerability is a classic CWE-502 (Deserialization of Untrusted Data) issue in PHP, where attacker-controlled input reaches a call to PHP's unserialize() (or an equivalent deserialization sink) without validation. In PHP, deserializing untrusted data instantiates objects whose magic methods (__wakeup, __destruct, __toString) fire automatically; an attacker chains these across the theme, WordPress core, and any active plugin to build a 'POP chain' that performs unintended actions. The affected component is the AI ANN commercial WordPress theme (CPE cpe:2.3:a:axiomthemes:ai_ann), a product from the AxiomThemes catalog. The concrete impact depends on which gadget classes are loadable at runtime, which is why object-injection flaws are highly deployment-dependent even when the injection point itself is unauthenticated.

RemediationAI

No vendor-released patched version is identified at time of analysis, so a fixed release could not be confirmed from the available data - monitor the Patchstack advisory (https://patchstack.com/database/wordpress/theme/ann/vulnerability/wordpress-ai-ann-theme-1-29-0-php-object-injection-vulnerability) and the AxiomThemes vendor channel for an update beyond 1.29.0 and apply it immediately once released. Until a patch exists, consider deploying a WAF/virtual patch (Patchstack offers one) to block serialized-object payloads reaching the vulnerable endpoint, and restrict or disable the specific theme feature that accepts external input if it can be identified; note that WAF rules can be bypassed by encoding and disabling features may break site functionality. As defense in depth, remove or deactivate unused plugins to shrink the pool of exploitable POP gadgets, and if the theme is not essential, switch to a maintained theme. Do not rely on obscurity - the injection point is unauthenticated.