dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-13595

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 CIBELES AI 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.10.8. 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 CIBELES AI WordPress plugin versions up to 1.10.8 lacks proper capability checks in the actualizador_git.php file, enabling unauthenticated attackers to download arbitrary GitHub repositories and overwrite plugin files on the server, which can lead to remote code execution.

MitigationImmediately update to version 1.10.9 or later if available, or remove/disable the plugin until a patch is released, as this unauthenticated arbitrary file upload vulnerability allows complete site compromise.

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 CIBELES AI plugin is installed
    Check the WordPress plugins directory or use WP CLI: wp plugin list --name='cibeles-ai' or inspect /wp-content/plugins/ directory for a folder named 'cibeles-ai' or similar
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Identify installed plugin version
    Check the plugin main file header in /wp-content/plugins/[cibeles-ai-folder]/cibeles-ai.php for the 'Version' comment, or use WP CLI: wp plugin get cibeles-ai --field=version
    Affected if The version is below 1.10.9 or cannot be determined (older than fixed release)
  3. Locate vulnerable file actualizador_git.php
    Check if /wp-content/plugins/[cibeles-ai-folder]/actualizador_git.php exists on the server filesystem
    Affected if The file exists and is readable via the web server
  4. Verify endpoint accessibility
    Attempt to access the actualizador_git.php file via HTTP/HTTPS request (e.g., https://yourdomain.com/wp-content/plugins/cibeles-ai/actualizador_git.php) or verify via file permissions that it is web-accessible
    Affected if The file responds to HTTP requests without requiring authentication
  5. Confirm plugin is active
    Use WP CLI: wp plugin is-active cibeles-ai, or check WordPress admin plugins page
    Affected if The plugin is active and the vulnerable file is accessible

If the CIBELES AI plugin is installed at any version below 1.10.9 with the actualizador_git.php file present and web-accessible, the environment is affected by this unauthenticated RCE vulnerability.

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

Immediately update to version 1.10.9 or later if available, or remove/disable the plugin until a patch is released, as this unauthenticated arbitrary file upload vulnerability allows complete site compromise.

Recommended fix High confidence

Version 1.10.9 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the CIBELES AI plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is functioning correctly

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