Skip to main content
VulnerabilityPublished

CVE-2026-131755: Successful Redirection for Contact Form (WordPress plugin) · Cross-site Scripting

Affects Successful Redirection for Contact Form (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 2.0.1 soon.

Data as of 22 Nov 2026, 16:37 UTC

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

Thin evidence

One scorer or none
CVSS scores by source
CNA (Patchstack)CVSS 3.17.1
Patch
Available – fixed in 2.0.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 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 21 Nov 2026.

What to do

Upgrade Successful Redirection for Contact Form (WordPress plugin) to 2.0.1.

Affected software

ProductAffectedFixed in
Successful Redirection for Contact Formcf7-redirectionAffected
  • <2.0.1
Fixed in
  • 2.0.1

AI-suggested

Upgrade the Successful Redirection for Contact Form plugin to version 2.0.1 or later, where this vulnerability has been fixed. No other mitigation steps are indicated by the vendor advisory.

Description

CVE-2026-131755 is a reflected Cross-site Scripting (XSS) vulnerability in the Successful Redirection for Contact Form plugin by Jayasree TU. The flaw allows improper neutralization of input during web page generation, which can lead to execution of malicious scripts when users interact with the affected contact form. Versions from initial releases up to 2.0.0 are affected. The issue is fixed in version 2.0.1.

References

Community reviews

Loading reviews…