CVE-2026-12123: All-in-One Video Gallery SSRF Vulnerability in WordPress
The All-in-One Video Gallery plugin for WordPress contains a Server-Side Request Forgery (SSRF) vulnerability affecting all versions through 4.8.5. An attacker with subscriber-level WordPress access can exploit this flaw by inserting a malicious URL into a video post, then triggering an unauthenticated download endpoint that forces the server to fetch and return that URL's content. This allows the attacker to reach internal systems, access sensitive data, or modify services that should only be accessible internally.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 6.4 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
- Weaknesses (CWE)
- CWE-918
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-07-10 / 2026-07-10
NVD description (verbatim)
The All-in-One Video Gallery plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 4.8.5 via the 'vdl' parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. A Subscriber-level attacker can plant an internal or loopback URL in the `mp4` post meta of a newly created `aiovg_videos` post via XML-RPC `wp.newPost`, then trigger the unauthenticated `?vdl=<post_id>` endpoint to force the server to fetch that URL and stream the full response body back to the requester.
12 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
The vulnerability exists in the `vdl` parameter of the All-in-One Video Gallery plugin's download functionality. The attack chain involves two steps: (1) A subscriber-level attacker uses XML-RPC's `wp.newPost` to create or modify an `aiovg_videos` post, injecting a malicious URL into the `mp4` post meta field; (2) The attacker then accesses the unauthenticated `?vdl=<post_id>` endpoint, which retrieves the URL from the post meta and makes a server-side request to it, returning the full response body to the requester. The lack of proper input validation and outbound request filtering allows the plugin to reach internal IP addresses, loopback interfaces, and services not exposed to the internet.
Business impact
Organizations using this plugin face exposure of internal services and data. An attacker can use the vulnerability to enumerate internal networks, access cloud metadata services (AWS, GCP, Azure), exfiltrate data from internal APIs, or interact with internal systems like databases and caching layers. Because the initial compromise only requires subscriber access—a role often granted to content creators—the barrier to exploitation is low, increasing organizational risk from insider threats and compromised user accounts.
Affected systems
All versions of the All-in-One Video Gallery plugin for WordPress up to and including version 4.8.5 are vulnerable. Any WordPress installation with this plugin installed and at least one user with subscriber-level or higher permissions is at risk. The vulnerability does not require the attacker to be an authenticated site administrator; subscriber accounts are sufficient.
Exploitability
Exploitability is moderate to high. The attack requires subscriber-level access, but WordPress sites frequently grant this role to content creators, freelancers, and contributors. Once a subscriber account is obtained—either through compromise, phishing, or legitimate access—exploitation is straightforward and requires no complex techniques. The unauthenticated download endpoint that triggers the SSRF can be accessed by any visitor to the site, amplifying risk if an attacker already controls a post on the site.
Remediation
Update the All-in-One Video Gallery plugin to a patched version released after 4.8.5. Verify the fix through the plugin's official repository or vendor advisory to confirm the version number. If an immediate patch is unavailable, temporarily disable the plugin or restrict XML-RPC access to trusted users only. Review user roles and revoke unnecessary subscriber access to limit the pool of potential attackers.
Patch guidance
Monitor the All-in-One Video Gallery plugin's official repository and vendor advisories for a security update addressing this SSRF vulnerability. Once available, apply the patch immediately to all affected WordPress installations. Before patching, consider temporarily deactivating the plugin to eliminate attack surface. Test the patched version in a staging environment to ensure compatibility with your theme and other plugins before deploying to production.
Detection guidance
Monitor web server logs for unusual patterns in the `vdl` parameter, particularly requests containing localhost, 127.0.0.1, internal IP ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), or cloud metadata endpoints (169.254.169.254). Watch for XML-RPC `wp.newPost` calls from subscriber-level accounts, especially those creating or modifying `aiovg_videos` posts with suspicious `mp4` meta values. Review access logs for the unauthenticated download endpoint immediately following such posts. Implement Web Application Firewall rules to block outbound requests to private IP ranges originating from the plugin.
Why prioritize this
Although the CVSS score is 6.4 (Medium), the practical risk is elevated because the vulnerability requires only subscriber-level access, a role widely distributed across WordPress sites. The ability to reach internal systems and services, combined with the low barrier to exploitation, makes this a priority fix for organizations running WordPress with this plugin. Ransomware and data exfiltration campaigns increasingly leverage SSRF vulnerabilities to move laterally into internal networks.
Risk score, explained
The CVSS 3.1 score of 6.4 reflects a network-accessible vulnerability requiring low privileges (subscriber access) with no user interaction, affecting confidentiality and integrity but not availability. The score is appropriate for the technical severity, but operational risk is higher due to the prevalence of subscriber accounts on typical WordPress sites and the value of internal network access to attackers.
Frequently asked questions
Do we need to be an administrator to exploit this?
No. Any user with subscriber-level access or higher can exploit this vulnerability. Subscriber is a standard role granted to content contributors, making the barrier to exploitation relatively low compared to admin-only flaws.
Can this vulnerability be exploited without any account at all?
Partial exploitation is possible without an account. An attacker can trigger the SSRF by accessing the unauthenticated ?vdl endpoint if a malicious post already exists. However, injecting the malicious URL into a post requires at least subscriber-level access, typically via XML-RPC.
What internal systems are most at risk?
Cloud metadata services (AWS/GCP/Azure), internal APIs, databases accessible via HTTP, internal wikis, CI/CD systems, and management consoles are common targets. Attackers often probe for metadata endpoints to steal credentials and API keys.
What should we do if we cannot patch immediately?
Disable the plugin if it is not critical to operations. If it must remain active, restrict XML-RPC access to trusted IP ranges and audit subscriber account permissions, removing access for users who no longer need it. Monitor logs closely for suspicious vdl parameter usage.
This analysis is provided for informational purposes and does not constitute professional security advice. Verify all patch version numbers, release dates, and remediation steps against the official plugin repository and vendor advisories before implementation. CVSS scores and vulnerability classifications are subject to interpretation and may vary based on organizational context. Perform thorough testing in non-production environments before deploying patches. SEC.co assumes no liability for the accuracy or completeness of this analysis or its application to any specific environment. Source: NVD (public-domain), retrieved 2026-08-17. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2025-36324MEDIUMIBM watsonx.data Intelligence SSRF Vulnerability - Patch & Detection Guide
- CVE-2025-58175MEDIUMGeoServer SSRF Vulnerability in Proxy Configuration
- CVE-2026-0285MEDIUMPAN-OS Server-Side Request Forgery (SSRF) – Palo Alto Networks
- CVE-2026-10052MEDIUMQuay SSRF in LDAP/SMTP Validation—Internal Network Reconnaissance Risk
- CVE-2026-10177MEDIUMSSRF in Aider-AI Aider 0.86.3 AWS Metadata Endpoint
- CVE-2026-10239MEDIUMJeecgBoot Server-Side Request Forgery (SSRF) in Word Editing Module
- CVE-2026-10240MEDIUMJeecgBoot SSRF Vulnerability in /airag/airagModel/test Endpoint
- CVE-2026-10241MEDIUMJimuReport SSRF in File Download Function – Patch to 3.9.2