CVE-2019-15071
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 · uneditedThe "/cgi-bin/go" page in MAIL2000 through version 6.0 and 7.0 has a cross-site scripting (XSS) vulnerability, allowing execution of arbitrary code via ACTION parameter without authentication. The code can executed for any user accessing the page. This vulnerability affects many mail system of governments, organizations, companies and universities.
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 confidenceCross-site scripting (XSS) vulnerability in MAIL2000 mail server versions 6.0 and 7.0, specifically in the /cgi-bin/go page via the ACTION parameter. The vulnerability allows unauthenticated attackers to inject and execute arbitrary JavaScript code in users' browsers, potentially leading to session hijacking or credential theft.
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>= 6.0, <= 7.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Mail2000 installationIdentify if Openfind Mail2000 mail server is deployed in your environment by checking running services, installed software inventory, or web server configuration for Mail2000 components.Affected if Mail2000 mail server is present in the environment
-
Determine installed versionLocate the Mail2000 version information typically found in the product itself, administration console, or system documentation. Compare your version against the affected range: 6.0 through 7.0.Affected if Installed version is greater than or equal to 6.0 and less than or equal to 7.0
-
Locate vulnerable CGI endpointCheck if the /cgi-bin/go endpoint is accessible on your Mail2000 server by attempting to access it via HTTP/HTTPS or reviewing web server configuration files that map this path.Affected if The /cgi-bin/go endpoint exists and responds to requests
-
Verify ACTION parameter handlingExamine how the ACTION parameter is processed when requests are made to /cgi-bin/go. Submit a test request with a benign parameter value and inspect whether the value is reflected in the response without proper encoding.Affected if The ACTION parameter value from the request is reflected in the page output without sanitization or encoding
You are affected if Mail2000 version 6.0 through 7.0 is installed and the /cgi-bin/go endpoint with the ACTION parameter reflects user input without sanitization.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict input validation and output encoding on the ACTION parameter in /cgi-bin/go to prevent XSS. Given CVSS 6.1 Medium severity, prioritize remediation but the low privileged nature and user interaction requirement slightly reduces immediate risk.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15071 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-15071 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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