dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-13597

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-25
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 AI Feeds plugin for WordPress is vulnerable to arbitrary file uploads due to missing capability check in the 'actualizador_git.php' file in all versions up to, and including, 1.0.11. This makes it possible for unauthenticated attackers to download arbitrary GitHub repositories and overwrite plugin files on the affected site's server which may make remote code execution possible.

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 AI Feeds WordPress plugin contains a missing capability check in the 'actualizador_git.php' file, allowing unauthenticated attackers to download arbitrary GitHub repositories and overwrite plugin files on the server, leading to potential remote code execution.

MitigationUpdate the AI Feeds plugin to version 1.0.12 or later; if immediate updating is not feasible, remove or disable the vulnerable 'actualizador_git.php' file and implement WAF rules to block access to this 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. Confirm AI Feeds plugin is installed
    Check the WordPress plugins directory at wp-content/plugins/ for the 'ai-feeds' or similar AI Feeds plugin folder. Also check via WordPress admin dashboard under Plugins.
    Affected if The AI Feeds plugin folder exists in the WordPress installation.
  2. Identify installed plugin version
    Open the main plugin file (usually ai-feeds.php or similar in the plugin folder) and look for the version comment/header, or check the version in the WordPress admin plugins list.
    Affected if The installed version is lower than 1.0.12.
  3. Locate the vulnerable file
    Check if the file 'actualizador_git.php' exists in the plugin directory. Search for this specific filename within the AI Feeds plugin folder.
    Affected if The file 'actualizador_git.php' exists in the plugin directory.
  4. Verify file is accessible
    Attempt to access the file directly via browser: visit yoursite.com/wp-content/plugins/ai-feeds/actualizador_git.php (adjust path based on actual plugin folder name). Check if the file responds or returns an error rather than a 404.
    Affected if The file returns a response other than 404 (not removed, renamed, or blocked).

A user is affected if the AI Feeds plugin is installed with a version before 1.0.12 AND the 'actualizador_git.php' file exists and is accessible on the server.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the AI Feeds plugin to version 1.0.12 or later; if immediate updating is not feasible, remove or disable the vulnerable 'actualizador_git.php' file and implement WAF rules to block access to this endpoint.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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