CVE-2005-1284
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 addnew script in Argosoft Mail Server Pro 1.8.7.6 allows remote attackers to create arbitrary accounts, even if "Allow Creation of Accounts From the Web Interface" is disabled, via a direct HTTP POST request.
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 confidenceArgosoft Mail Server Pro 1.8.7.6 contains an authorization bypass vulnerability in the addnew script. When the 'Allow Creation of Accounts From the Web Interface' setting is disabled, the web interface properly hides account creation functionality. However, the underlying addnew script does not validate this configuration setting when receiving direct HTTP POST requests, allowing remote attackers to create arbitrary user accounts without authentication.
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= 1.8.7.6CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 Argosoft Mail Server versionCheck the installed version of Argosoft Mail Server. This can typically be found in the program files directory, in the Windows registry under HKLM\Software\Argosoft\MailServer, or via the About section of the management interface. Compare your installed version to 1.8.7.6.Affected if The installed version is exactly 1.8.7.6.
-
Verify web interface statusCheck whether the Argosoft Mail Server web interface is running and accessible. This is typically hosted on a specific port (often 8080 or 8181). Attempt to access the web interface URL.Affected if The web interface is accessible and running.
-
Check account creation configurationLocate and examine the 'Allow Creation of Accounts From the Web Interface' setting in the Argosoft Mail Server configuration. This is typically found in the web interface settings or in the server configuration file (usually mailserver.ini or similar in the program data directory).Affected if The setting is explicitly disabled (set to false or no), meaning the web UI hides account creation but the underlying script may still process requests.
-
Verify addnew script accessibilityAttempt to access the addnew script directly via HTTP POST without authentication. The script is typically located at a path like /addnew or /mail/addnew on the web interface. Use a tool like curl to send a POST request to create a test account, or inspect the script code if accessible.Affected if The addnew script processes the request and creates an account without requiring authentication, regardless of the configuration setting.
You are affected if you are running version 1.8.7.6, the web interface is accessible, and the addnew script can create accounts without authentication even when the account creation setting is disabled.
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 dataApply vendor patch if available, or modify the addnew script to check the 'Allow Creation of Accounts From the Web Interface' configuration setting before processing account creation requests. Alternatively, disable the web interface entirely if not required.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-1284 — 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-2005-1284 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