The A2Reviews WordPress plugin through 1.2.3 does not properly verify authorization on several of its API command
Source GCVE Database
Not known to be exploited.
Data as of 15 Nov 2026, 10:38 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 15 Nov 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 14 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| A2Reviews | Affected
| Fixed in– |
Description
The A2Reviews WordPress plugin up to version 1.2.3 has an authorization flaw in several API command handlers. This flaw allows unauthenticated attackers to modify plugin settings and product review metadata, as well as read non-public product metadata. The issue arises because the plugin relies on a signature keyed on a value that is empty by default on unconnected installs, leading to improper authorization verification.