Is Media Cleaner safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (7.3.6). As of 2026-11-04. 2 issues are on record for older versions; version 7.0.4 or newer fixes all of them that state a fix. Keep Media Cleaner on the latest version (7.3.6) and remove it if you do not use it.

Which versions of Media Cleaner are vulnerable?

Known issues on record (newest first): Server-side request forgery (SSRF) (7.0.3 and older, fixed in 7.0.4); Information disclosure (6.7.2 and older, fixed in 6.7.3). The full list with sources is on this page.

What is the latest version of Media Cleaner?

7.3.6, according to wordpress.org (last updated 2026-11-03). It has 90,000+ active installs.

What should I do if my Media Cleaner is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update media-cleaner). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · media-cleaner · data as of 2026-11-04

Is Media Cleaner safe? Known vulnerabilities and latest version

Latest version: 7.3.6
Last updated: 2026-11-03
Active installs: 90,000+
Known issues on record: 2
Unpatched in latest: 0
Tested up to WP: 7.1.4 · PHP 8.1+

Find and delete unused images and media files, fix broken entries, with a trash to undo anything. A lighter, faster WordPress! 💕 — by Jordy Meow

What to do

Update to the latest version (7.3.6). Anything older than 7.0.4 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get media-cleaner --field=version shows what you run; wp plugin update media-cleaner updates it.

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 4.1 CVE-2026-4912 · published 2026-07-28

Server-side request forgery (SSRF) in Media Cleaner (7.0.3 and older)

Affected: 7.0.3 and older
Fixed in: 7.0.4 *
Access needed (per CVSS): Needs an admin-level account
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Media Cleaner: Clean your WordPress! plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 7.0.3. This is due to the `get_urls_from_html()` function using `DOMDocument::loadHTMLFile()` to fetch iframe source URLs with an insufficient hostname validation check that relies on a substring match against the site's server name. This makes it possible for authenticated attackers, with Administrator-level access and above, to make web requests to arbitrary locations originating from the web application, which can be used to query and interact with internal services.

NVD CVE-2026-4912 Wordfence advisory Code change (fix)Plugin source

medium 5.3 CVE-2024-33922 · published 2024-05-02

Information disclosure in Media Cleaner (6.7.2 and older)

Affected: 6.7.2 and older
Fixed in: 6.7.3
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Insertion of Sensitive Information into Log File vulnerability in Jordy Meow WP Media Cleaner.This issue affects WP Media Cleaner: from n/a through 6.7.2.

NVD CVE-2024-33922 Patchstack advisory

Recent activity

2026-11-03 — latest release on wordpress.org (7.3.6).
2026-07-28 — Server-side request forgery (SSRF) disclosed (CVE-2026-4912), fixed in 7.0.4.
2024-05-02 — Information disclosure disclosed (CVE-2024-33922), fixed in 6.7.3.

Free. We check the CVE feeds every day and email you only when a new issue for Media Cleaner (media-cleaner) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Server-side request forgery (SSRF) (1) · Sensitive data exposure (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/media-cleaner (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/media-cleaner"><img src="https://laskyr.com/plugins/media-cleaner/badge.svg" alt="Media Cleaner vulnerability status"></a>

← Check another plugin · Free hacked-site scan