Media Library FoldersWordPress extension · Maxfoundry
CVE-2022-41634
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Media Library Folders plugin <= 7.1.1 on WordPress.
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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability exists in the Media Library Folders WordPress plugin version 7.1.1 and earlier. The vulnerability allows attackers to trick authenticated administrators into unknowingly performing unwanted actions via maliciously crafted requests, potentially leading to unauthorized manipulation of the media library folder structure.
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
Media Library FoldersWordPress extension
< 7.1.2CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Verify Media Library Folders plugin is installedLog into WordPress admin and navigate to Plugins > Installed Plugins, or check the filesystem at wp-content/plugins/ for a folder named 'media-library-folders' or similarAffected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionIn WordPress admin, find Media Library Folders in the plugins list and read the version number from the plugin row, or open the main plugin PHP file and check the 'Version' header in the plugin comment blockAffected if The version displayed is 7.1.1 or any version number lower than 7.1.2
-
Confirm the plugin handles folder operationsAccess the Media Library Folders feature in the WordPress admin dashboard (typically under Media > Folders or a similar menu item) and verify that you can create, rename, move, or delete foldersAffected if You can perform folder manipulation actions and the plugin is at version 7.1.1 or earlier
Your environment is affected if the Media Library Folders plugin is installed at version 7.1.1 or earlier and handles folder structure operations without CSRF token validation for authenticated administrator sessions.
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 · scoped7.1.2
Update the Media Library Folders plugin to version 7.2 or later, which includes proper CSRF token validation for state-changing operations. Additionally, enforce SameSite cookies and implement nonces for all administrative actions.
Media Library Folders version 7.1.2 or later
- Backup your WordPress site database and files before making any changes
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Find 'Media Library Folders' in the plugin list
- Click 'Update now' if an update is available, or manually update to version 7.1.2 or later
- Verify the plugin is running version 7.1.2 or higher after updating
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Media Library Folders
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41634 — 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-2022-41634 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