dbcve.org
Mp Form Mail CgiApplication · Futomi

CVE-2018-0514

CRITICAL · 9.8 CVSS v3.0 Published 2018-02-08
Fix available
A fix is available. Upgrade to after 2.0.13 or later.
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
MP Form Mail CGI eCommerce Edition Ver 2.0.13 and earlier allows remote attackers to execute arbitrary OS commands via unspecified vectors.

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 · moderate confidence

This is a critical command injection vulnerability in MP Form Mail CGI eCommerce Edition versions 2.0.13 and earlier. The flaw allows remote attackers to execute arbitrary operating system commands on the target server, likely through unsanitized user input being passed to system calls.

MitigationUpdate to a patched version if available, or implement strict input validation and avoid passing user-supplied data to system/exec functions. If patching is not possible, restrict CGI script permissions and network access.

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
Mp Form Mail CgiApplication
Affected:<= 2.0.13

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.0/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. Locate MP Form Mail CGI script
    Search the web server document root and cgi-bin directories for files named 'mpformmail.cgi', 'formmail.cgi', or similar form handling CGI scripts from Futomi. Common locations include /var/www/cgi-bin/, /usr/local/apache/cgi-bin/, or within site-specific directories.
    Affected if The script file exists on the server in a web-accessible location
  2. Identify installed version
    Open the located CGI script file and search for a version string. Look for comments near the top of the file, or variables like '$VERSION', '$version', or 'Version:' in the script contents. Alternatively, if the script has a version display feature, access it via web request.
    Affected if The version is 2.0.13 or earlier, or no version information is found (treat as potentially vulnerable)
  3. Verify CGI script is web-accessible
    Check the web server configuration (Apache httpd.conf, nginx config, or .htaccess files) to confirm the MP Form Mail CGI script is configured as a handler for form submissions and is accessible via HTTP/HTTPS from the web.
    Affected if The script is configured as an active CGI handler and reachable via web requests
  4. Confirm user input handling
    Review the CGI script source code to verify it processes user-submitted form data. Look for parameter handling routines that process input fields which would be passed to the mail sending functionality.
    Affected if The script processes and uses user-supplied form input for its normal operation (this is the intended function but also the attack vector)
  5. Check for command execution functions
    Search the CGI script source code for calls to system(), exec(), backticks (`), open() with pipe operators, or similar functions that execute OS commands. Determine if any user-controlled input flows to these functions without proper sanitization.
    Affected if User input from form fields can reach system/exec functions without sanitization

The server is affected if MP Form Mail CGI eCommerce Edition version 2.0.13 or earlier is installed and accessible via the web, as the vulnerability allows remote command injection through unsanitized form 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.

From vendor data
Upgrade available Upgrade to a release after 2.0.13
Interim mitigation

Update to a patched version if available, or implement strict input validation and avoid passing user-supplied data to system/exec functions. If patching is not possible, restrict CGI script permissions and network access.

Fix this in Mp Form Mail Cgi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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