CVE-2026-65507: AIWU (WordPress plugin) · Incorrect Privilege Assignment
Affects AIWU (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 5 Nov 2026, 00:01 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SergeyAIWU | Affected
| Fixed in– |
AI-suggested
Until an official fix is released, restrict network access to the affected software where possible and monitor for suspicious activity related to privilege escalation attempts. Avoid exposing vulnerable versions to untrusted networks.
Description
CVE-2026-65507 is a critical vulnerability in Sergey AIWU versions up to and including 1.5.6 that allows unauthenticated privilege escalation due to incorrect privilege assignment (CWE-266). This flaw enables an attacker with no prior authentication to gain elevated privileges, potentially leading to full system compromise. The vulnerability has a CVSS v3.1 score of 9.8, indicating high impact on confidentiality, integrity, and availability. No official patch or remediation guidance is currently available from the vendor. There are no known exploits in the wild at this time.