CVE-2025-9562
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-10-18

Last updated on: 2025-10-21

Assigner: Wordfence

Description
The Redirection for Contact Form 7 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's qs_date shortcode in all versions up to, and including, 3.2.6 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-10-18
Last Modified
2025-10-21
Generated
2026-05-07
AI Q&A
2025-10-18
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
themeisle redirection_for_contact_form_7 3.2.6
themeisle redirection_for_contact_form_7 3.2.7
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2025-9562 is a Stored Cross-Site Scripting (XSS) vulnerability in the Redirection for Contact Form 7 WordPress plugin. It occurs due to insufficient input sanitization and output escaping on user-supplied attributes in the plugin's qs_date shortcode. Authenticated attackers with contributor-level access or higher can inject arbitrary JavaScript code into pages, which executes whenever a user accesses those pages.


How can this vulnerability impact me? :

This vulnerability allows authenticated users with contributor-level access or above to inject malicious scripts into the website. These scripts can execute in the context of other users visiting the affected pages, potentially leading to theft of sensitive information, session hijacking, defacement, or other malicious actions that compromise website security and user trust.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability could negatively impact compliance with standards like GDPR and HIPAA by exposing user data to unauthorized access through malicious script execution. Stored XSS can lead to data breaches or unauthorized data processing, which are violations of these regulations. Although the plugin supports GDPR compliance features such as data export and erase requests, the presence of this vulnerability undermines the overall security posture required for compliance. [1]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

Detection of this vulnerability involves identifying if the vulnerable version (up to and including 3.2.6) of the Redirection for Contact Form 7 plugin is installed on your WordPress site. Since the vulnerability is a Stored Cross-Site Scripting via the qs_date shortcode, you can check for the presence of this shortcode in your site content or posts. Additionally, monitoring for unusual script injections or unexpected JavaScript execution in pages using this shortcode may help detect exploitation attempts. There are no specific network commands provided in the resources. However, you can use WordPress CLI commands to check the plugin version, for example: `wp plugin list --status=active` to see if the vulnerable plugin version is active. Also, scanning your site content for the shortcode `[qs_date]` with suspicious attributes might help. No explicit commands for detection are provided in the resources. [1, 4]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include updating the Redirection for Contact Form 7 plugin to version 3.2.7 or later, as this update addresses the vulnerability by improving data sanitization and output escaping. If updating immediately is not possible, restrict contributor-level access to trusted users only, since the vulnerability requires authenticated users with contributor-level access or higher to exploit. Additionally, review and sanitize any user-supplied attributes in the qs_date shortcode usage manually. Applying security best practices such as using a Web Application Firewall (WAF) to block malicious scripts and monitoring for suspicious activity is also recommended. [1, 4]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart