dbcve.org
WekanApplication · Wekan Project

CVE-2018-1000549

MEDIUM · 5.3 CVSS v3.0 Published 2018-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
Wekan version 1.04.0 contains a Email / Username Enumeration vulnerability in Register' and 'Forgot your password?' pages that can result in A remote attacker could perform a brute force attack to obtain valid usernames and email addresses.. This attack appear to be exploitable via HTTP 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 confidence

Wekan 1.04.0 has a user enumeration vulnerability in the Register and 'Forgot your password?' pages. These pages return different HTTP responses or error messages depending on whether an email address or username is already registered, allowing attackers to discover valid accounts via brute force enumeration.

MitigationModify both pages to return identical, generic responses (e.g., 'If an account exists with this email, a reset link has been sent') regardless of whether the submitted email/username exists in the system, preventing enumeration through response differentiation.

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
WekanApplication
Affected:= 1.04.0

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
Low
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Wekan version
    Check the Wekan web interface footer, API endpoint (e.g., /api/version), or Docker container tags to determine the exact version number
    Affected if version is exactly 1.04.0 (other versions may not be affected)
  2. Test Register page with non-existent email
    Navigate to the Register page and submit a form with an email address that is guaranteed NOT to exist in your system (e.g., [email protected]). Record the exact HTTP response code and any error/success message displayed.
    Affected if page returns any specific error message or response indicating the email does not exist
  3. Test Register page with existing email
    Navigate to the Register page and submit a form using an email address that you know IS already registered in your Wekan instance. Record the exact HTTP response code and any error/success message displayed.
    Affected if page returns a different response than the non-existent test (e.g., 'email already registered' vs generic message)
  4. Test Forgot Password page with non-existent email
    Navigate to the 'Forgot your password?' page and submit a form with an email address that does NOT exist in your system. Record the exact response displayed.
    Affected if page shows any indication that the email does not exist or returns a different response than for existing accounts
  5. Test Forgot Password page with existing email
    Navigate to the 'Forgot your password?' page and submit a form using an email address that IS registered in your Wekan instance. Record the exact response displayed.
    Affected if page returns a different response than the non-existent test (e.g., confirmation that reset email was sent vs indication that no account exists)

You are affected if your installed Wekan version is 1.04.0 AND the Register or Forgot Password pages return measurably different responses for existing versus non-existing email addresses or usernames, allowing an attacker to enumerate valid accounts.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Modify both pages to return identical, generic responses (e.g., 'If an account exists with this email, a reset link has been sent') regardless of whether the submitted email/username exists in the system, preventing enumeration through response differentiation.

Fix this in Wekan Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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