The Surfer WordPress plugin before 1.8.1.759 discloses a sensitive API credential to low-privileged users through the
Source GCVE Database
Not known to be exploited : upgrade to 1.8.1.759 soon.
Data as of 6 Nov 2026, 07:21 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 1.8.1.759
Exploitation evidence
Disclosed: evidence found.
CVE published 6 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 5 Nov 2026.
What to do
Upgrade Surfer (WordPress plugin) to 1.8.1.759.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Surfer | Affected
| Fixed in
|
AI-suggested
Patch to version 1.8.1.759 or later where this vulnerability is fixed. Since the affected versions are prior to 1.8.1.759, upgrading the plugin to this version or newer will remediate the issue.
Description
The Surfer WordPress plugin versions before 1.8.1.759 expose a sensitive API credential on the post editor page to users with contributor-level access and above. This credential is used as the sole authorization mechanism for privileged REST API actions, enabling these users to escalate their privileges to publish arbitrary posts and perform other restricted operations.