CVE-2019-15073
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 · uneditedAn Open Redirect vulnerability for all browsers in MAIL2000 through version 6.0 and 7.0, which will redirect to a malicious site without authentication. 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 confidenceAn Open Redirect vulnerability in MAIL2000 mail software versions 6.0 and 7.0 allows unauthenticated remote attackers to craft malicious URLs that redirect users to arbitrary external websites. This affects the webmail interface and occurs due to insufficient validation of redirect parameters.
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.
-
Identify Mail2000 versionLocate the installed version of Openfind Mail2000 by checking software inventory, vendor documentation, or system configuration files. Compare the version number to the affected range: 6.0 through 7.0.Affected if The installed version falls between 6.0 and 7.0 inclusive.
-
Confirm webmail interface exposureDetermine whether the Mail2000 webmail interface is network-accessible by reviewing firewall rules, reverse proxy configurations, and external access policies.Affected if The webmail interface is accessible to users over the network.
-
Locate redirect parameters in webmail URLsAnalyze webmail-generated URLs during login, logout, and link navigation to identify parameters that control page redirection (commonly named 'redirect', 'url', 'next', or similar).Affected if The webmail uses redirect parameters to direct users to different pages.
-
Test redirect parameter for external domain acceptanceConstruct a test URL using the redirect parameter with an external domain (such as ?redirect=http://example.com) and verify if the application permits redirection to that external site without blocking or validating the target.Affected if The application allows redirection to arbitrary external domains without restriction.
-
Inspect URL validation controlsReview any existing URL validation logic, allowlist filtering, or WAF configurations that may already mitigate this vulnerability in the deployment.Affected if No URL validation or allowlist filtering is implemented on redirect parameters.
The environment is affected if Mail2000 versions 6.0-7.0 are deployed with an accessible webmail interface that permits unrestricted external redirects through URL parameters.
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 dataUpgrade to a patched version of MAIL2000 if available, or implement strict URL validation/allowlist filtering on redirect parameters to prevent external domain redirection. Consider deploying a WAF rule to block suspicious redirect patterns.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15073 — 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-15073 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