CVE-2026-4161
Stored XSS in Review Map by RevuKangaroo Plugin Settings
Publication date: 2026-03-21
Last updated on: 2026-03-21
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| revukangaroo | the_review_map | to 1.7 (inc) |
| revukangaroo | review_map_by_revukangaroo | to 1.7 (inc) |
Helpful Resources
Exploitability
| 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
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?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know
Can you explain this vulnerability to me?
The Review Map by RevuKangaroo plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in all versions up to and including 1.7. This vulnerability arises because the plugin does not properly sanitize input or escape output in its settings. As a result, an authenticated attacker with administrator-level access or higher can inject malicious web scripts into pages. These scripts will execute whenever a user accesses the affected page.
This vulnerability specifically affects multi-site WordPress installations or installations where the unfiltered_html capability has been disabled.
How can this vulnerability impact me? :
This vulnerability allows an attacker with administrator-level access to inject malicious scripts that execute in the context of users visiting the affected pages. This can lead to unauthorized actions such as stealing user credentials, hijacking user sessions, or performing actions on behalf of users without their consent.
Since the vulnerability requires high privileges to exploit, the risk is somewhat limited to environments where such access is possible. However, in multi-site installations or where unfiltered_html is disabled, the impact can be significant due to the potential for widespread script execution.