Skip to main content
VulnerabilityPublished

CVE-2026-107713: Flutterwave Payments (WordPress plugin) · Cross-site Scripting

Affects Flutterwave Payments (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.2 High.

Data as of 21 Nov 2026, 08:13 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.17.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 20 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
flutterwaveFlutterwave PaymentsAffected
  • <=1.0.7
Fixed in–

AI-suggested

Users should upgrade once a fixed version is released. Until then, consider disabling the vulnerable plugin or removing the affected shortcodes from front-end pages to prevent exposure. Monitor the vendor's advisory channels for updates. Since the nonce is publicly exposed, relying on it for authentication is ineffective, so additional input validation or filtering at the application or web server level may help mitigate risk temporarily.

Description

The Flutterwave Payments plugin for WordPress up to version 1.0.7 is vulnerable to stored Cross-Site Scripting (XSS) via the 'form_id' parameter. This vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary scripts. The exploit is facilitated because the nonce required for storing input is publicly exposed on front-end pages rendering certain plugin shortcodes, enabling attackers to scrape and reuse it.

References

Community reviews

Loading reviews…