CVE-2024-30486
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Max Foundry Media Library Folders.This issue affects Media Library Folders: from n/a through 8.1.7.
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 · moderate confidenceSQL injection vulnerability in Max Foundry Media Library Folders plugin allows attackers to inject malicious SQL commands via unsanitized user input. The vulnerability affects all versions through 8.1.7 and could allow unauthorized database access, data exfiltration, or manipulation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 8.1.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Media Library Folders plugin is installedAccess WordPress admin panel and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'media-library-folders' or similar Max Foundry plugin folderAffected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionIn WordPress admin, find the Media Library Folders entry in the Plugins list and read the version number from the plugin description row, or open the main plugin PHP file and locate the 'Version' header in the plugin comment blockAffected if The version number displayed is less than 8.1.8
-
Verify the plugin is activeCheck the Plugins page in WordPress admin - the plugin must be activated for the SQL injection to be exploitableAffected if The plugin status shows as 'Active'
-
Confirm vulnerable version rangeCompare the installed version against the affected range: all versions through 8.1.7 are vulnerable (version 8.1.8 contains the fix)Affected if Installed version is 8.1.7 or earlier
If the Media Library Folders plugin is installed, active, and running a version lower than 8.1.8, the environment is affected by CVE-2024-30486 and vulnerable to SQL injection attacks.
Generated from the published advisory. Verify against your own configuration.
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 · scoped8.1.8
Update Media Library Folders plugin to version 8.1.8 or later which contains the fix for the SQL injection vulnerability. If immediate update is not possible, restrict administrative access to trusted users only.
8.1.8
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Media Library Folders' in the plugin list
- Check if the current version is below 8.1.8
- If vulnerable, click 'Update Now' to install version 8.1.8
- After update, verify the plugin version shows 8.1.8
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-30486 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-30486 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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