Easy Media ReplaceWordPress extension · Easy Media Replace Project
CVE-2022-46850
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 · uneditedAuth. (author+) Broken Access Control vulnerability leading to Arbitrary File Deletion in Nabil Lemsieh Easy Media Replace plugin <= 0.1.3 versions.
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 confidenceAuthenticated users with author-level or higher privileges can delete arbitrary files on the server due to missing capability checks and improper input validation in the Easy Media Replace plugin versions 0.1.3 and below. The broken access control allows any privileged user to manipulate file paths beyond the intended scope.
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
Easy Media ReplaceWordPress extension
<= 0.1.3CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 Easy Media Replace plugin is installedCheck WordPress plugins directory or access Plugins page in WordPress admin to confirm Easy Media Replace plugin is presentAffected if Plugin is installed and active in WordPress
-
Determine installed plugin versionView plugin details in WordPress admin or inspect plugin header file to read the Version fieldAffected if Version is 0.1.3 or below
-
Confirm WordPress user roles existCheck WordPress users list to identify if any users have author, editor, or administrator rolesAffected if At least one user with author-level or higher privileges exists in the system
-
Verify plugin file deletion functionality is accessibleInspect plugin code for delete file functions or test if the media replacement feature accepts file path parametersAffected if The file deletion or media replace feature is accessible to authenticated users
User is affected if Easy Media Replace plugin version 0.1.3 or below is installed and active with at least one user having author-level or higher privileges and the vulnerable file operation feature is accessible
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 · scopedUpdate to the latest version of Easy Media Replace plugin that implements proper authorization checks and path validation, or remove the plugin if no patched version is available.
- 1. Remove the Easy Media Replace plugin from the WordPress installation immediately, as the plugin appears to be abandoned with no security updates available.
- 2. Search for an alternative media replacement plugin that is actively maintained and has recent security updates.
- 3. If file deletion functionality is specifically needed, implement a custom solution with proper authorization checks or use a reputable plugin with verified security audit history.
- 4. Review the WordPress site for any signs of compromise that may have occurred due to this vulnerability.
- 5. Implement regular security audits and monitoring for all installed plugins, especially those not regularly updated.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Easy Media Replace
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46850 — 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-46850 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