dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-12957

HIGH · 8.8 CVSS v3.1 Published 2026-01-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 arbitrary file upload in all versions up to, and including, 4.5.7. This is due to insufficient file type validation detecting VTT files, allowing double extension files to bypass sanitization while being accepted as a valid VTT file. This makes it possible for authenticated attackers, with author-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.

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.5.7) lacks proper file type validation for VTT (Web Video Text Track) files, allowing double extension payloads (e.g., shell.php.vtt) to bypass sanitization checks. Authenticated users with author-level permissions or higher can upload malicious files that may execute arbitrary code on the server.

MitigationUpdate the All-in-One Video Gallery plugin to a version beyond 4.5.7; if immediate update is not feasible, restrict author-level user permissions and implement server-side file type validation for uploads.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm the All-in-One Video Gallery plugin is installed
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and search for 'All-in-One Video Gallery' or 'aiovg'. If found, note the plugin status (active/inactive).
    Affected if The plugin is installed and active in WordPress.
  2. Identify the installed plugin version
    In the Plugins list, locate the All-in-One Video Gallery entry and read the version number displayed beneath the plugin name. Compare this version to the affected range (versions up to and including 4.5.7).
    Affected if The installed version is 4.5.7 or lower.
  3. Check for author-level or higher user accounts
    In WordPress admin, go to Users > All Users. Review the Role column for each account. Identify users assigned roles of Author, Editor, Administrator, or any custom role with equivalent or higher upload permissions.
    Affected if At least one user account has Author-level permissions or higher.
  4. Inspect uploads directory for VTT files with double extensions
    Access the WordPress uploads folder (typically /wp-content/uploads/). Search for files matching patterns such as *.php.vtt, *.php.txt, or other double extensions commonly used in upload bypass attacks. Use file manager or command-line: find /path/to/uploads -name '*.php.*'
    Affected if Files with double extensions (especially .php.vtt or similar) exist in the uploads directory.
  5. Review recent media library uploads for suspicious VTT files
    In WordPress admin, go to Media > Library. Filter or sort by upload date. Look for VTT files uploaded recently, especially if the uploader has author-level permissions. Check file names for unusual patterns.
    Affected if VTT files with unexpected names or sizes have been uploaded by author-level users.

A user is affected if the All-in-One Video Gallery plugin versions 4.5.7 or lower is installed and active, and author-level or higher user accounts exist in the WordPress environment.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the All-in-One Video Gallery plugin to a version beyond 4.5.7; if immediate update is not feasible, restrict author-level user permissions and implement server-side file type validation for uploads.

Recommended fix Moderate confidence

4.5.8 or later

  1. 1. Update the All-in-One Video Gallery plugin to the latest available version from the WordPress plugin repository
  2. 2. Verify the update was successful by checking the installed version number
  3. 3. Confirm that file upload functionality still works as expected for legitimate VTT files
  4. 4. Review any recently uploaded files on the server to ensure no malicious files were uploaded during the vulnerability window

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12957 — 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-2025-12957 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