dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2013-10039

HIGH · 8.7 CVSS v4.0 Published 2025-07-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
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
A command injection vulnerability exists in GestioIP 3.0 commit ac67be and earlier in ip_checkhost.cgi. Crafted input to the 'ip' parameter allows attackers to execute arbitrary shell commands on the server via embedded base64-encoded payloads. Authentication may be required depending on deployment configuration.

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

A command injection vulnerability in GestioIP 3.0's ip_checkhost.cgi allows attackers to execute arbitrary shell commands via the 'ip' parameter by embedding base64-encoded payloads. The lack of proper input sanitization on this parameter enables OS command injection.

MitigationImplement strict input validation and sanitization on the 'ip' parameter to reject or escape shell metacharacters, and ensure the web application runs with minimal system privileges to limit blast radius.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Locate GestioIP installation
    Search common installation paths such as /usr/local/gestioip, /var/www/gestioip, or /opt/gestioip. Check for directories named 'gestioip' on the system.
    Affected if GestioIP is found installed on the system
  2. Identify GestioIP version
    Check the installed version by looking at version files, release notes, or the main script headers in the GestioIP installation directory. Compare against version 3.0.
    Affected if The installed version is GestioIP 3.0 or earlier
  3. Find ip_checkhost.cgi script
    Locate the ip_checkhost.cgi file within the GestioIP web directory, typically under cgi-bin/ or similar web-accessible paths.
    Affected if The ip_checkhost.cgi script exists in the installation
  4. Verify web CGI interface is enabled
    Check if the web server has CGI execution enabled for the GestioIP cgi-bin directory. Look at Apache/nginx configuration for ScriptAlias or cgi-bin permissions.
    Affected if CGI execution is enabled and the GestioIP web interface is accessible over HTTP/HTTPS
  5. Inspect ip parameter handling in ip_checkhost.cgi
    Examine the source code of ip_checkhost.cgi to see how the 'ip' parameter is processed. Look for unsanitized use in shell commands, system(), exec(), or backtick operations.
    Affected if The 'ip' parameter is used in shell commands without proper input sanitization or validation

If GestioIP version 3.0 is installed with the ip_checkhost.cgi script accessible via a CGI-enabled web interface and the 'ip' parameter is processed without sanitization, the environment is affected by this command injection 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

Implement strict input validation and sanitization on the 'ip' parameter to reject or escape shell metacharacters, and ensure the web application runs with minimal system privileges to limit blast radius.

Recommended fix Moderate confidence

GestioIP 3.0.1 or later (latest stable release)

  1. 1. Identify the current GestioIP version in use by checking the installation directory or running 'gestioip --version' if available
  2. 2. Download the latest GestioIP release from the official SourceForge repository at https://sourceforge.net/projects/gestioip/
  3. 3. Review the release notes or changelog for version 3.0.1 or later to confirm the command injection fix is included
  4. 4. Backup the current GestioIP installation, including configuration files and database
  5. 5. Stop the web server service (e.g., Apache, Nginx) that serves GestioIP
  6. 6. Extract the new version files, overwriting the existing ip_checkhost.cgi and other affected files
  7. 7. Restore custom configurations from the backup if needed
  8. 8. Restart the web server service
Caveat Review custom configurations and ensure compatibility with the new version, as default file paths or dependencies may have changed

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

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-2013-10039 — 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-2013-10039 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