dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-12123

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The All-in-One Video Gallery WordPress plugin versions up to 4.8.5 contain an authenticated SSRF vulnerability via the 'vdl' parameter. Attackers with subscriber-level access can use XML-RPC to inject a malicious URL into post metadata, then trigger the vulnerable endpoint to force the server to fetch and return arbitrary internal/loopback URLs.

MitigationUpdate the plugin to a patched version (4.8.6 or higher), or implement server-side validation to reject internal/loopback IP addresses and restrict URL schemes in the 'vdl' parameter processing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin version
    Locate the plugin's main file (e.g., all-in-one-video-gallery.php) in wp-content/plugins/ and read the version header, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' and check plugin file headers
    Affected if The installed version is 4.8.5 or lower
  2. Confirm XML-RPC is enabled
    Access the XML-RPC endpoint at /xmlrpc.php and verify it responds (or check via WordPress admin > Settings > Writing > XML-RPC), or test with a pingback request
    Affected if XML-RPC is enabled and accepts requests
  3. Check for subscriber-level user accounts
    Query the WordPress users table: SELECT user_login, user_email FROM wp_users WHERE ID IN (SELECT user_id FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%subscriber%')
    Affected if At least one subscriber-level user account exists
  4. Identify vulnerable endpoint usage
    Review server access logs for requests to the plugin's endpoints containing the 'vdl' parameter, or examine the plugin source code for the handler that processes the 'vdl' parameter in post metadata
    Affected if The plugin processes 'vdl' parameter values from post metadata without validating whether they point to internal/loopback addresses

A user is affected if the All-in-One Video Gallery plugin version is 4.8.5 or lower AND XML-RPC is enabled AND at least one subscriber-level user account exists, allowing injection of malicious URLs via the 'vdl' parameter to trigger SSRF.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a patched version (4.8.6 or higher), or implement server-side validation to reject internal/loopback IP addresses and restrict URL schemes in the 'vdl' parameter processing.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12123 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12123 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data