Quick answers
- Is CVE-2026-115277 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115277 being exploited in the wild.
- How severe is CVE-2026-115277?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- weDevs User Frontend before 4.3.14.
- Is there a fix for CVE-2026-115277?
- Yes: fixed in 4.3.14. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115277 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-115277?
- Check whether you run weDevs User Frontend 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.
How to fix
- Fixed in: 4.3.14
Technical details
The plugin fails to sanitize and escape user-supplied values in the 'field_attr' parameter before reflecting them into HTML attributes in an AJAX response. The vulnerable endpoint is protected by an anonymous nonce that only validates for logged-out requests, meaning the XSS payload executes against unauthenticated visitors rather than authenticated users. An attacker can craft a malicious URL to trigger the vulnerability without authentication.
Affected products
- Wedevs User Frontend before 4.3.14
Timeline
- 2026-10-28: disclosed
- 2026-10-30: advisory