CVE-2026-1706
Reflected XSS in All-in-One Video Gallery Plugin
Publication date: 2026-03-04
Last updated on: 2026-03-04
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordfence | all-in-one_video_gallery | to 4.7.1 (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
Can you explain this vulnerability to me?
The All-in-One Video Gallery plugin for WordPress has a Reflected Cross-Site Scripting (XSS) vulnerability in the 'vi' parameter in all versions up to and including 4.7.1. This vulnerability arises because the plugin does not properly sanitize or escape input from this parameter. As a result, an unauthenticated attacker can inject arbitrary web scripts that execute in the context of a user's browser if the user is tricked into clicking a malicious link containing the crafted 'vi' parameter.
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute malicious scripts in the browsers of users who click on specially crafted links. The impact includes the potential theft of user credentials, session hijacking, defacement of the website, or redirection to malicious sites. Since the attack is reflected and requires user interaction (clicking a link), it can be used in phishing attacks to compromise user security and privacy.
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?
[{'type': 'paragraph', 'content': "The vulnerability involves Reflected Cross-Site Scripting (XSS) via the 'vi' parameter in the All-in-One Video Gallery WordPress plugin versions up to 4.7.1. Detection can focus on monitoring HTTP requests to the affected site for suspicious or malicious payloads in the 'vi' parameter."}, {'type': 'paragraph', 'content': "One way to detect attempts is to look for HTTP GET requests containing the 'vi' parameter with suspicious script tags or encoded JavaScript payloads."}, {'type': 'list_item', 'content': "Use web server access logs to search for requests with the 'vi' parameter containing suspicious input, for example using grep:"}, {'type': 'list_item', 'content': "grep -i 'vi=.*<script' /var/log/apache2/access.log"}, {'type': 'list_item', 'content': "Or use a network monitoring tool or Intrusion Detection System (IDS) to alert on HTTP requests with suspicious 'vi' parameter values."}, {'type': 'list_item', 'content': "Use curl or wget to test the endpoint manually by injecting a harmless test payload in the 'vi' parameter and observe if it is reflected unsanitized in the response."}, {'type': 'list_item', 'content': 'Example curl command to test for reflected XSS:'}, {'type': 'list_item', 'content': "curl -G 'https://example.com/path-to-video-gallery' --data-urlencode 'vi=<script>alert(1)</script>' -v"}, {'type': 'paragraph', 'content': 'If the response contains the injected script tag without proper escaping or sanitization, the vulnerability is present.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': "The primary mitigation is to update the All-in-One Video Gallery plugin to version 4.7.5 or later, where the vulnerability is fixed by sanitizing the 'vi' parameter using WordPress's sanitize_text_field() function."}, {'type': 'paragraph', 'content': "If immediate update is not possible, consider implementing Web Application Firewall (WAF) rules to block or sanitize requests containing suspicious input in the 'vi' parameter."}, {'type': 'paragraph', 'content': 'Additionally, educate users to avoid clicking on suspicious links that may exploit this reflected XSS vulnerability.'}, {'type': 'paragraph', 'content': 'Review and apply security best practices such as disabling unnecessary plugins, limiting user input where possible, and monitoring logs for suspicious activity.'}] [1]