All-in-One Video Gallery <= 4.8.5 - Authenticated (Subscriber+) Server-Side Request Forgery via 'vdl' Parameter
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.
Quick answer
All-in-One Video Gallery should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- *-4.8.5
Fixed versions
- 4.9.0
How to fix it
All-in-One Video Gallery is affected by CVE-2026-12123, a server-side request forgery issue in versions up to 4.8.5. Wordfence lists the official remediation as updating to version 4.9.0, or a newer patched version. Prioritize internet-facing WordPress sites, sites with public registration, customer portals, Elementor/page-builder surfaces, and admin workflows where the vulnerable feature is enabled. If immediate patching is not possible, disable the affected plugin or feature, restrict access, and monitor for exploitation until the update is installed.
- Inventory every WordPress site that has All-in-One Video Gallery installed, including production, staging, multisite, client, and WooCommerce environments.
- Confirm the installed All-in-One Video Gallery version and compare it with the affected range from the Wordfence advisory.
- Update All-in-One Video Gallery to version 4.9.0, or to a newer vendor-supported patched version from the official WordPress update channel.
- If the update cannot be applied immediately, disable All-in-One Video Gallery or the affected feature and restrict access with roles, authentication, WAF rules, or temporary route blocking.
- Review outbound HTTP logs, webhook activity, metadata endpoint access, internal service requests, and unusual callbacks triggered by the WordPress site.
- Rotate administrator sessions, API keys, webhook secrets, payment or integration tokens, and affected credentials if logs or content review suggest compromise.
- Clear WordPress, object, CDN, page-builder, security plugin, and browser caches after patching so vulnerable assets or stored payloads are not served.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the running All-in-One Video Gallery version is version 4.9.0 or newer, and record the patched version in the remediation ticket.
- Verify attackers cannot make the site request arbitrary internal, metadata, loopback, or private-network URLs through the affected feature.
- Review web server, WordPress, security plugin, WAF, database, and application logs for exploitation attempts before and after the fix.
- Retest normal visitor, subscriber, customer, editor, administrator, checkout, form, API, booking, or integration workflows to confirm expected behavior still works.
- Run a fresh Fixnx scan and document the public exposure state, patched version, log review, and any cleanup evidence.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-12123?
All-in-One Video Gallery versions listed as affected should be reviewed: *-4.8.5.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.