dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-7667

HIGH · 8.1 CVSS v3.1 Published 2025-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

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 Restrict File Access plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1.2. This is due to missing or incorrect nonce validation on the 'restrict-file-access' page. This makes it possible for unauthenticated attackers to to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php), via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 Restrict File Access WordPress plugin versions up to 1.1.2 lacks proper nonce validation on its admin page, allowing unauthenticated attackers to forge administrative requests that can delete arbitrary files on the server. If critical files like wp-config.php are deleted, this can lead to remote code execution.

MitigationUpdate the Restrict File Access plugin to version 1.1.3 or later which includes proper nonce validation. Until patched, administrators should avoid clicking untrusted links while logged into WordPress admin.

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Locate the Restrict File Access plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins. Find 'Restrict File Access' in the list and read the version number displayed beneath the plugin name. Alternatively, inspect the plugin's main PHP file (usually /wp-content/plugins/restrict-file-access/ restrict-file-access.php) and look for a Version header in the file comments.
    Affected if the displayed version is 1.1.2 or any version lower than 1.1.2
  2. Confirm the plugin is active
    In the same plugins list, verify that the Restrict File Access plugin has an 'Active' status indicator (typically a green border or 'Activate' link is absent).
    Affected if the plugin is currently active and the version is 1.1.2 or lower
  3. Check for the vulnerable admin handler
    Inspect the plugin's main PHP file for the admin page handler that processes file deletion requests. Look for code that handles a 'delete' or 'file' parameter without calling wp_verify_nonce() or check_admin_referer() before performing file operations.
    Affected if the code lacks nonce verification logic before processing deletion requests and the plugin version is 1.1.2 or lower

A user is affected if the Restrict File Access plugin is installed, active, and running at version 1.1.2 or below, enabling unauthenticated attackers to delete arbitrary files via forged administrative requests.

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 Restrict File Access plugin to version 1.1.3 or later which includes proper nonce validation. Until patched, administrators should avoid clicking untrusted links while logged into WordPress admin.

Recommended fix Moderate confidence

Version 1.1.3 or later (latest version available in the WordPress plugin repository)

  1. Check the WordPress plugin repository for the Restrict File Access plugin at plugins.wordpress.org to identify the current version
  2. Update the plugin to the latest available version (version 1.1.3 or later) from the WordPress admin dashboard under Plugins > All Plugins
  3. Alternatively, navigate to Plugins > Add New > Upload and upload the latest version from the official WordPress plugin repository
  4. After updating, verify the plugin is active and functioning correctly
  5. Consider reviewing other security settings and ensuring the site is not vulnerable to other CSRF issues

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-7667 — 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-7667 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