Quick answers
- Is CVE-2026-108484 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108484 being exploited in the wild.
- How severe is CVE-2026-108484?
- High severity, with a CVSS score of 7.1, published 14 October 2026.
- Which products and versions are affected?
- WPManageNinja Best Payments Plugin for WP through 4.6.27.
- Is there a fix for CVE-2026-108484?
- Yes: fixed in 4.6.28. Until then: If unable to update immediately, use a WordPress security plugin such as Patchstack to block exploitation attempts until the patch can be applied. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-108484 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-108484?
- Check whether you run WPManageNinja Best Payments Plugin for WP 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.6.28
If unable to update immediately, use a WordPress security plugin such as Patchstack to block exploitation attempts until the patch can be applied.
Technical details
A stored XSS vulnerability in the Best Payments Plugin for WP through version 4.6.27 fails to properly sanitize user input during web page generation. The vulnerability can be exploited by an unauthenticated attacker, though user interaction (such as clicking a malicious link or visiting a crafted page) is required for successful exploitation. Injected scripts persist in the database and execute for all visitors viewing the affected content.
Affected products
- WPManageNinja Best Payments Plugin for WP through 4.6.27
Timeline
- 2026-10-14: disclosed
- 2026-10-12: patched: Version 4.6.28 released as fix