CVE-2026-1931
Received Received - Intake
Stored XSS in Rent Fetch WordPress Plugin Allows Script Injection

Publication date: 2026-02-18

Last updated on: 2026-02-18

Assigner: Wordfence

Description
The Rent Fetch plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'keyword' parameter in all versions up to, and including, 0.32.4 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for unauthenticated attackers 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
2026-02-18
Last Modified
2026-02-18
Generated
2026-05-27
AI Q&A
2026-02-18
EPSS Evaluated
2026-05-25
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
brindledigital rent_fetch to 0.32.4 (inc)
brindledigital rent_fetch 0.32.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?

The Rent Fetch plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in all versions up to and including 0.32.4. This vulnerability arises because the plugin does not properly sanitize or escape user input supplied via the 'keyword' parameter. As a result, an unauthenticated attacker can inject malicious web scripts into pages. These scripts execute whenever a user accesses the affected page, potentially compromising user security.


How can this vulnerability impact me? :

This vulnerability can allow attackers to execute arbitrary scripts in the context of users visiting the affected pages. The impact includes the potential for attackers to steal sensitive information such as cookies or session tokens, perform actions on behalf of users without their consent, or deface the website. Since the vulnerability is exploitable without authentication, it poses a significant risk to all users interacting with the plugin.


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

I don't know


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

The vulnerability in the Rent Fetch WordPress plugin is a Stored Cross-Site Scripting (XSS) issue via the 'keyword' parameter. Detection involves identifying if the plugin version is up to and including 0.32.4 and if the 'keyword' parameter is being exploited to inject scripts.

Since the vulnerability involves injection of arbitrary web scripts through the 'keyword' parameter, detection can be done by monitoring HTTP requests for suspicious or encoded script tags in the 'keyword' parameter.

Suggested commands for detection include using network monitoring tools or web server logs to search for suspicious payloads. For example, using grep on web server logs to find requests containing script tags or suspicious JavaScript in the 'keyword' parameter:

  • grep -i 'keyword=.*<script' /var/log/apache2/access.log
  • grep -i 'keyword=.*%3Cscript' /var/log/apache2/access.log

Additionally, scanning the WordPress installation to check the plugin version can help identify vulnerable instances:

  • Check plugin version in WordPress admin dashboard or by inspecting the plugin's main file header for version number.
  • Use WP-CLI command: wp plugin get rent-fetch --field=version

What immediate steps should I take to mitigate this vulnerability?

[{'type': 'paragraph', 'content': 'Immediate mitigation steps include updating the Rent Fetch plugin to a version that contains the security fix for CVE-2026-1931, which addresses the stored XSS vulnerability by sanitizing and escaping user input and output.'}, {'type': 'paragraph', 'content': "If an update is not immediately possible, consider disabling or restricting access to the vulnerable plugin functionality, especially the search features that use the 'keyword' parameter."}, {'type': 'paragraph', 'content': 'Additional mitigation steps include:'}, {'type': 'list_item', 'content': 'Apply the patch that introduces sanitization of search parameters and escaping of output as described in the fix (see Resource 4).'}, {'type': 'list_item', 'content': "Implement Web Application Firewall (WAF) rules to block requests containing suspicious script injections in the 'keyword' parameter."}, {'type': 'list_item', 'content': "Regularly monitor logs for suspicious activity targeting the 'keyword' parameter."}, {'type': 'list_item', 'content': 'Ensure that WordPress, plugins, and themes are kept up to date with security patches.'}] [4]


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