Quick answers
- Is CVE-2026-111110 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111110 being exploited in the wild.
- How severe is CVE-2026-111110?
- High severity, with a CVSS score of 7.2, published 17 October 2026.
- Which products and versions are affected?
- AyeCode GetPaid up to and including 2.8.61.
- Is there a fix for CVE-2026-111110?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-111110 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-111110?
- Check whether you run AyeCode GetPaid at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The plugin suffers from stored cross-site scripting (XSS) in the 'mmdwqzpoxadd' parameter due to insufficient input sanitization and output escaping. An unauthenticated attacker can inject arbitrary JavaScript that persists in the database and executes when an administrator accesses the Payment Form Details metabox; the attack is possible because the nonce (getpaid_form_nonce) is publicly exposed via wp_localize_script, eliminating the need for authentication or nonce leakage.
Affected products
- AyeCode GetPaid up to and including 2.8.61
Timeline
- 2026-10-17: disclosed