dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2025-7778

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Icons Factory plugin for WordPress is vulnerable to Arbitrary File Deletion due to insufficient authorization and improper path validation within the delete_files() function in all versions up to, and including, 1.6.12. 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).

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 Icons Factory WordPress plugin has an arbitrary file deletion vulnerability in its delete_files() function. The function lacks proper authorization checks (allowing unauthenticated attackers) and fails to validate file paths, enabling deletion of any file on the server accessible to the web server user.

MitigationUpdate the plugin to version 1.6.13 or later. If no patch is available, disable the plugin immediately and consider deploying WAF rules to block requests to the vulnerable endpoint.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Verify Icons Factory plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Icons Factory' or check the /wp-content/plugins/ directory for an icons-factory folder
    Affected if The plugin is present in the installation
  2. Check installed plugin version
    In WordPress admin, find Icons Factory in the plugins list and view the version number displayed, or read the main plugin PHP file and look for 'Version:' in the plugin header comment
    Affected if The version is lower than 1.6.13 or cannot be determined
  3. Identify the vulnerable delete endpoint
    Check the plugin files for the delete_files() function and its associated AJAX action or direct URL endpoint. Look in main plugin PHP files and any API handler classes for 'delete_files' or 'delete' related actions
    Affected if The delete_files function exists and is hooked to a WordPress action accessible to unauthenticated users
  4. Confirm missing authorization checks
    Review the delete_files() function code to verify it does not call current_user_can(), is_admin(), or similar authorization checks before performing file deletion operations
    Affected if The function contains no authorization checks before file deletion logic
  5. Check for path traversal vulnerability
    Review the delete_files() function to see if it validates or sanitizes the file path parameter, looking for functions like realpath(), basename(), or whitelist checks
    Affected if The function accepts a file path parameter without validating it is within an allowed directory

A user is affected if the Icons Factory plugin is installed with a version below 1.6.13 and the delete_files() function is accessible without authentication or path validation.

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 1.6.13 or later. If no patch is available, disable the plugin immediately and consider deploying WAF rules to block requests to the vulnerable endpoint.

Recommended fix High confidence

Icons Factory version 1.6.13

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Icons Factory' plugin
  4. If an update is available, click 'Update Now' to update to version 1.6.13
  5. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload the fixed version 1.6.13 of the Icons Factory plugin
  6. Verify the plugin is now running version 1.6.13

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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