dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-6043

HIGH · 8.1 CVSS v3.1 Published 2025-07-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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 Malcure Malware Scanner — #1 Toolset for WordPress Malware Removal plugin for WordPress is vulnerable to Arbitrary File Deletion due to a missing capability check on the wpmr_delete_file() function in all versions up to, and including, 17.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary files making remote code execution possible. This is only exploitable when advanced mode is enabled on the site.

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 Malcure Malware Scanner WordPress plugin has a missing capability check on the wpmr_delete_file() function, allowing authenticated users with Subscriber-level access or higher to delete arbitrary files on the server. This arbitrary file deletion vulnerability is exploitable only when advanced mode is enabled and can lead to remote code execution by allowing attackers to delete critical files.

MitigationUpdate the plugin to version 17.1 or later which should include the proper capability check. Until updated, disable advanced mode and ensure user registration is restricted to prevent untrusted users from gaining subscriber-level access.

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Malcure Malware Scanner plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Malcure Malware Scanner' or check wp-content/plugins directory for the malcure-malware-scanner folder
    Affected if The plugin is not installed or not active - no action needed. If found, continue to version check.
  2. Check installed plugin version against 17.1
    In WordPress admin Plugins list, find Malcure Malware Scanner and note the version number displayed. Compare this to the fixed version 17.1
    Affected if Version is 17.1 or higher - vulnerability is patched. If version is below 17.1, continue to advanced mode check.
  3. Verify if Advanced Mode is enabled
    Access the plugin settings in WordPress admin - typically under Malcure MS > Settings or a similar settings page. Look for an 'Advanced Mode' toggle or option and note whether it is turned on
    Affected if Advanced Mode is disabled - exploitation is not possible. If Advanced Mode is enabled, the vulnerability is exploitable on this installation.
  4. Identify subscriber-level user accounts
    In WordPress admin, go to Users > All Users and review the Role column. Note any accounts assigned 'Subscriber' role, especially those created for external or untrusted users
    Affected if Only trusted administrators or editors have accounts - limited risk. If untrusted or external users have Subscriber-level access, they can exploit this vulnerability.

You are affected if the plugin version is below 17.1 AND Advanced Mode is enabled AND untrusted users can obtain Subscriber-level access to your WordPress 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 version 17.1 or later which should include the proper capability check. Until updated, disable advanced mode and ensure user registration is restricted to prevent untrusted users from gaining subscriber-level access.

Recommended fix Moderate confidence

Latest version of Malcure Malware Scanner plugin (version > 17.0)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate the 'Malcure Malware Scanner' plugin.
  4. 4. Check the current version installed (should be 17.0 or lower based on the vulnerability description).
  5. 5. If an update is available, click 'Update Now' to install the latest version which contains the security fix.
  6. 6. If no update appears, manually download the latest version from the WordPress plugin repository and reinstall.
  7. 7. After updating, verify that the wpmr_delete_file() function now includes proper capability checks (e.g., current_user_can('manage_options')).
  8. 8. Confirm the update was successful by checking the plugin version number.
Caveat Minimal risk - security update typically does not break existing functionality; always test in staging first

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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