CVE-2026-104677: WP Coder · Code Injection
Affects WP CoderSource CVE Database V5
Not known to be exploited · CVSS 7.2 High : upgrade to 4.5.2 soon.
Data as of 21 Nov 2026, 17:34 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.5.2
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 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 21 Nov 2026.
What to do
Upgrade WP Coder to 4.5.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WP Coder | Affected
| Fixed in
|
AI-suggested
Upgrade WP Coder to version 4.5.2 or later, where this vulnerability is fixed by restricting the PHP code-execution feature to administrators only. If you cannot patch yet, restrict Editor-level user capabilities or remove the plugin if possible.
Description
The WP Coder WordPress plugin before 4.5.2 does not restrict access to its PHP code-execution feature to administrators, gating it on a content capability that the Editor role holds by default, which allows Editor-level users to save and execute arbitrary PHP code on the server and fully compromise the site.