The AppPresser WordPress plugin before 5.0.0 does not properly escape the contents of its debug log when displaying it
Source GCVE Database
Not known to be exploited : upgrade to 5.0.0 soon.
Data as of 19 Nov 2026, 10:51 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 5.0.0
Exploitation evidence
Disclosed: evidence found.
CVE published 19 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 18 Nov 2026.
What to do
Upgrade AppPresser (WordPress plugin) to 5.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AppPresser | Affected
| Fixed in
|
AI-suggested
Administrators should be cautious when accessing debug logs and restrict access to trusted users only.
Description
The AppPresser WordPress plugin versions prior to 5.0.0 contain a vulnerability where the debug log contents are not properly escaped when displayed in the admin dashboard. This improper escaping, combined with decoding of escape sequences after sanitization, allows unauthenticated users to perform stored cross-site scripting (XSS) attacks against administrators if debug logging is enabled.