dbcve.org
AutocaliwebApplication · Gelbphoenix

CVE-2025-7404

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-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
Public exploit 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
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in Calibre Web, Autocaliweb allows Blind OS Command Injection.This issue affects Calibre Web: 0.6.24 (Nicolette); Autocaliweb: from 0.7.0 before 0.7.1.

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

Calibre Web and Autocaliweb contain an OS Command Injection vulnerability allowing remote attackers to execute arbitrary OS commands via improperly neutralized special elements. This is a blind command injection, meaning the attacker may not see direct output but can still execute commands on the underlying system.

MitigationUpgrade Autocaliweb to version 0.7.1 or later to resolve the command injection vulnerability. If upgrading is not immediately possible, restrict network access to the application and implement input validation at network boundaries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AutocaliwebApplication
Affected:= 0.7.0
Calibre WebApplication
Affected:= 0.6.24

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. Identify running Calibre Web or Autocaliweb instance
    Check for web processes listening on common ports (8083, 8084 for Calibre Web) or examine running Python processes: ps aux | grep -i calibre or ps aux | grep -i autocli
    Affected if Either Calibre Web or Autocaliweb is running as a web service
  2. Check Calibre Web version
    Visit the /about page of the Calibre Web interface, or check the version file in the installation directory (version.py or __init__.py), or run: grep -r 'version' in the application root
    Affected if Version is exactly 0.6.24
  3. Check Autocaliweb version
    Examine the version.py or setup.py file in the Autocaliweb installation directory, or check the application metadata: pip show autocaliweb
    Affected if Version is exactly 0.7.0
  4. Verify the web interface is exposed
    Confirm the application is accessible over HTTP/HTTPS and accepts user input through web forms, particularly any feature that interacts with the filesystem or external programs
    Affected if The web application is internet-facing or accepts user-supplied input that could reach OS command execution routines
  5. Review web server access logs for suspicious patterns
    Examine web server logs (access.log, error.log) for unusual patterns such as shell metacharacters (;, |, &&, $( ), backticks) in URL parameters or POST data, especially around conversion or download features
    Affected if Logs show command injection attempts or unusual characters in user request parameters

You are affected if Calibre Web version 0.6.24 or Autocaliweb version 0.7.0 is running and the web interface is exposed to untrusted input.

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

Upgrade Autocaliweb to version 0.7.1 or later to resolve the command injection vulnerability. If upgrading is not immediately possible, restrict network access to the application and implement input validation at network boundaries.

Recommended fix High confidence

Autocaliweb 0.7.1

  1. 1. Identify the currently installed version of Autocaliweb or Calibre Web in your environment
  2. 2. For Autocaliweb: Upgrade to version 0.7.1 or later which contains the fix for the OS command injection vulnerability
  3. 3. For Calibre Web: The description indicates version 0.6.24 is affected; consult the official Calibre Web repository for the patched release
  4. 4. After upgrading, verify the installation is running the patched version
  5. 5. Test that the application functions normally after the upgrade

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

Fix this in Autocaliweb 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-7404 — 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-7404 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