dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2025-58098

HIGH · 8.3 CVSS v3.1 Published 2025-12-05
Fix available
A fix is available. Upgrade to 2.4.66 or later.
See remediation →
89/100
Remediation priority · High
Remotely reachable 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
Apache HTTP Server 2.4.65 and earlier with Server Side Includes (SSI) enabled and mod_cgid (but not mod_cgi) passes the shell-escaped query string to #exec cmd="..." directives. This issue affects Apache HTTP Server before 2.4.66. Users are recommended to upgrade to version 2.4.66, which fixes the issue.

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

Command injection vulnerability in Apache HTTP Server where SSI #exec cmd='...' directives improperly handle query strings when mod_cgid (not mod_cgi) is used, allowing the shell-escaped query string to be passed to the command and potentially enabling remote code execution.

MitigationUpgrade to Apache HTTP Server 2.4.66 or later, or disable SSI/mod_cgid if not required for the application.

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
HTTP ServerWeb server / proxy
Affected:< 2.4.66

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

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. Check Apache HTTP Server version
    Run 'httpd -v' or 'apache2 -v' to get the server version number
    Affected if Version is below 2.4.66 (for example, 2.4.65, 2.4.64, etc.)
  2. Confirm mod_cgid is loaded
    Check the server configuration for 'LoadModule cgid_module' or run 'httpd -M' / 'apache2ctl -M' to list loaded modules
    Affected if mod_cgid (mod_cgid.so) is present and loaded; mod_cgi does not trigger this vulnerability
  3. Verify SSI is enabled
    Check configuration for 'AddOutputFilter INCLUDES .shtml' or 'AddType text/html .shtml' directives, or inspect running config for SSI filter being applied
    Affected if Server-side includes (SSI) with the INCLUDES filter are enabled for .shtml or other file types
  4. Check for #exec cmd directives in use
    Search web document root for .shtml files containing '#exec cmd=' or 'cmd="' patterns using: 'find /var/www -name "*.shtml" -exec grep -l "#exec.*cmd" {} \;'
    Affected if Any .shtml files contain SSI #exec cmd= directives that could receive query string input

Affected if running Apache HTTP Server below version 2.4.66 with mod_cgid enabled AND SSI #exec cmd directives in use, as mod_cgi is not vulnerable to this specific flaw.

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
Upgrade available Upgrade to 2.4.66 or later
Fixed in 2.4.66
Interim mitigation

Upgrade to Apache HTTP Server 2.4.66 or later, or disable SSI/mod_cgid if not required for the application.

Recommended fix High confidence

2.4.66

  1. Back up the current Apache HTTP Server configuration directory (typically /etc/httpd/ or /etc/apache2/) and web content
  2. Stop the Apache service using the appropriate command for your system (e.g., systemctl stop httpd or apachectl stop)
  3. Download Apache HTTP Server version 2.4.66 from the official Apache download site (httpd.apache.org)
  4. Install the new version using your system's package manager or by compiling from source, depending on your installation method
  5. Restore the backed-up configuration files to the appropriate directory
  6. Start the Apache service (e.g., systemctl start httpd or apachectl start)
  7. Verify the installed version matches 2.4.66 using 'httpd -v' or 'apachectl -v'
  8. Test that the server is functioning properly and SSI directives work as expected
Caveat Minor version upgrade within 2.4.x series typically has minimal breaking changes; review the Apache 2.4.66 release notes for any specific configuration or module changes

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

Fix this in HTTP Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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