dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-13374

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-24
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 Kalrav AI Agent plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the kalrav_upload_file AJAX action in all versions up to, and including, 2.3.3. This makes it possible for unauthenticated attackers to upload arbitrary 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 Kalrav AI Agent WordPress plugin lacks file type validation in the kalrav_upload_file AJAX action (versions up to 2.3.3), allowing unauthenticated attackers to upload arbitrary files to the server, which can lead to remote code execution.

MitigationUpdate the Kalrav AI Agent plugin to a version beyond 2.3.3 that implements proper file type, extension, and MIME type validation, or disable the plugin until a patch is available.

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 Kalrav AI Agent plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Kalrav AI Agent' in the list
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed plugin version
    Click 'View Details' on the Kalrav AI Agent plugin in the WordPress plugins list to reveal the version number, or inspect the plugin main PHP file header for the 'Version' tag
    Affected if The version displayed is 2.3.3 or any lower version number
  3. Verify the vulnerable AJAX action exists
    Check the plugin PHP files for the presence of 'kalrav_upload_file' in wp_ajax_kalrav_upload_file and wp_ajax_nopriv_kalrav_upload_file action hooks (indicating both authenticated and unauthenticated access)
    Affected if Both wp_ajax_kalrav_upload_file and wp_ajax_nopriv_kalrav_upload_file hooks are registered without capability checks
  4. Inspect the upload handler for validation gaps
    Locate the function handling the kalrav_upload_file AJAX call and examine whether it performs file type, extension, or MIME type validation before moving uploaded files
    Affected if The handler function lacks file type/extension/MIME validation checks or uses only client-supplied values without server-side verification
  5. Check for suspicious uploaded files
    Examine the WordPress uploads directory (wp-content/uploads/) for executable files (php, phtml, js) or unknown files with extensions that should not be there, especially if they were uploaded recently
    Affected if Arbitrary or executable files exist in uploads that were not intentionally placed there

A user is affected if the Kalrav AI Agent plugin version is 2.3.3 or lower and the kalrav_upload_file AJAX action is registered without proper file type 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 Kalrav AI Agent plugin to a version beyond 2.3.3 that implements proper file type, extension, and MIME type validation, or disable the plugin until a patch is available.

Recommended fix Moderate confidence

Latest version available on wordpress.org/plugins/kalrav-ai-agent (version higher than 2.3.3)

  1. Check the WordPress admin dashboard under Plugins > Installed Plugins to confirm the current version of Kalrav AI Agent plugin
  2. Navigate to Plugins > Add New > Upload Plugin or check wordpress.org/plugins/kalrav-ai-agent for the latest version
  3. If a version newer than 2.3.3 is available, upload and install the updated plugin
  4. After upgrade, verify the kalrav_upload_file AJAX action now properly validates file types before allowing uploads
  5. If no newer version is available, consider temporarily disabling the Kalrav AI Agent plugin until a patched version is released
  6. Alternatively, contact the plugin vendor directly for patch timeline information
Caveat Review plugin changelog for any breaking changes between current version and upgrade target

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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