CVE-2026-115734: Pay with a tweet (WordPress plugin) · External Control of File Name or Path
Affects Pay with a tweet (WordPress plugin)Source CVE Database V5
Not known to be exploited.
Data as of 11 Nov 2026, 06:35 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 11 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 10 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Pay with a tweet | Affected
| Fixed in– |
AI-suggested
Users should immediately restrict access to the plugin's administrative functions and consider disabling or removing the plugin until a fix is available. Monitor vendor advisories for updates regarding a patch or official remediation.
Description
The Pay with a tweet WordPress plugin versions up to 1.0.5 contains a vulnerability where it does not validate file paths before deleting files and does not restrict access to administrative functions. This allows users with the Subscriber role to delete arbitrary files on the server, potentially leading to full site compromise.