dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2024-4670

HIGH · 8.8 CVSS v3.1 Published 2024-05-15
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 Local File Inclusion in all versions up to, and including, 3.6.5 via the aiovg_search_form shortcode. This makes it possible for authenticated attackers, with contributor-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

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 is vulnerable to Local File Inclusion (LFI) in versions up to 3.6.5 via the aiovg_search_form shortcode. Authenticated attackers with contributor-level access or higher can include and execute arbitrary files on the server, allowing execution of any PHP code contained in those files.

MitigationUpdate the plugin to a version beyond 3.6.5 once a patch is released; in the interim, restrict contributor-level user permissions and consider disabling the aiovg_search_form shortcode functionality.

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 plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'All-in-One Video Gallery' in the installed plugins list
    Affected if The plugin is not installed on the WordPress site
  2. Check the installed plugin version
    In the Plugins list, click on the plugin details or view the plugin header file (usually in wp-content/plugins/all-in-one-video-gallery/all-in-one-video-gallery.php) to read the Version: X.X.X comment
    Affected if The version number is 3.6.5 or lower
  3. Identify use of the vulnerable shortcode
    Search the WordPress database (wp_posts table) for posts containing '[aiovg_search_form' shortcode, or search theme files for this shortcode usage
    Affected if The aiovg_search_form shortcode is present in any post, page, or widget content
  4. Review user role permissions
    Go to WordPress admin > Users and identify any accounts with Contributor, Author, Editor, or Administrator roles since contributor-level access is sufficient for exploitation
    Affected if There are user accounts with contributor-level access or higher who could exploit this vulnerability

You are affected if the All-in-One Video Gallery plugin is installed at version 3.6.5 or lower AND the aiovg_search_form shortcode is in use AND contributor-level or higher users exist on the site.

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 plugin to a version beyond 3.6.5 once a patch is released; in the interim, restrict contributor-level user permissions and consider disabling the aiovg_search_form shortcode functionality.

Recommended fix High confidence

All-in-One Video Gallery version 3.6.6 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'All-in-One Video Gallery' plugin
  4. Check if the current version is 3.6.5 or lower
  5. If vulnerable, click 'Update Now' to update to the latest version (3.6.6 or later)
  6. Alternatively, download the latest version from wordpress.org/plugins/all-in-one-video-gallery/ and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the version number shows 3.6.6 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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