dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-7772

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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 Read in all versions up to, and including, 16.8 via the wpmr_inspect_file() function due to a missing capability check. This makes it possible for authenticated attackers, with subscriber-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.

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 an Arbitrary File Read vulnerability in the wpmr_inspect_file() function in versions up to 16.8. The function lacks a capability check, allowing any authenticated user with subscriber-level access or higher to read arbitrary files on the server by manipulating file path parameters.

MitigationUpdate the Malcure Malware Scanner plugin to version 16.9 or later. If an update is not available, disable the plugin temporarily and review server logs for indicators of compromise. Consider restricting file system permissions as an additional safeguard.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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. Verify Malcure Malware Scanner is installed
    Check your WordPress plugins directory or log into wp-admin and navigate to Plugins > Installed Plugins. Look for 'Malcure Malware Scanner' in the list.
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed plugin version
    In the WordPress admin Plugins page, click on the plugin name to view details, or inspect the main plugin file (usually malcure-malware-scanner/malcure.php) and look for the 'Version:' header in the plugin comments.
    Affected if The version listed is 16.8 or lower (versions 16.9 and later contain the fix)
  3. Confirm WordPress user accounts exist
    Log into wp-admin and go to Users > All Users, or query the wp_users table in the WordPress database.
    Affected if Any user account exists with a role of Subscriber or higher (the vulnerability affects any authenticated user)
  4. Inspect server access logs for exploitation attempts
    Review web server access logs (Apache, Nginx) for requests to endpoints that may invoke wpmr_inspect_file, such as AJAX calls to admin-ajax.php with action parameters related to file inspection, or direct plugin file access. Search for patterns like 'wpmr_inspect_file' or unusual file path parameters.
    Affected if Log entries show requests attempting to read sensitive files (e.g., wp-config.php, /etc/passwd) through plugin functionality

Your environment is affected if the Malcure Malware Scanner plugin is installed with version 16.8 or lower and any authenticated user account exists on the 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 Malcure Malware Scanner plugin to version 16.9 or later. If an update is not available, disable the plugin temporarily and review server logs for indicators of compromise. Consider restricting file system permissions as an additional safeguard.

Recommended fix Moderate confidence

Version 16.9 or later (check WordPress plugin repository for latest stable release)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Malcure Malware Scanner plugin
  4. Check if an update is available and update to the latest version
  5. Verify the update was successful by checking the plugin version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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