CVE-2017-1000141
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 issue was discovered in Mahara before 18.10.0. It mishandled user requests that could discontinue a user's ability to maintain their own account (changing username, changing primary email address, deleting account). The correct behavior was to either prompt them for their password and/or send a warning to their primary email address.
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 confidenceMahara before 18.10.0 fails to properly authenticate or warn users when making sensitive account changes including username changes, primary email address changes, and account deletion. The application should prompt for password confirmation and/or send a warning to the user's primary email address before allowing these actions, but instead allows them to proceed without proper verification.
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< 18.10.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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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 Mahara is installedAccess the Mahara application URL in a browser, or check the server for Mahara installation directories (typically under /var/www/html/ or similar web root). Look for Mahara-specific files like index.php, lib/version.php, or auth/lib.php.Affected if Mahara is present on the system
-
Identify the installed Mahara versionCheck the version file at <mahara_root>/lib/version.php and look for the $CFG->version variable, or log into the Mahara admin panel and navigate to Administration -> Site options -> About to view the version number.Affected if The version number cannot be determined or is below 18.10.0
-
Compare version against the affected rangeIf you found a version number, verify it is less than 18.10.0 (for example, 18.04.0, 17.10.0, 17.04.0, or earlier releases). Note that version 18.10.0 and later are NOT affected.Affected if Installed version is < 18.10.0 (e.g., 18.04.x, 17.10.x, etc.)
-
Test sensitive account change behavior (optional verification)Create a test user account, log in, and attempt to change the username or primary email address. Observe whether the application prompts for password confirmation before allowing the change, or check if a confirmation email is sent to the old email address.Affected if Password confirmation is NOT prompted and no notification email is sent before allowing sensitive account modifications
The environment is affected if Mahara is installed with a version lower than 18.10.0, as the application allows sensitive account changes without requiring password confirmation or sending warning notifications.
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 data18.10.0
Upgrade Mahara to version 18.10.0 or later which implements proper password confirmation and email notification for sensitive account changes. As a temporary measure, monitor account activity logs for unauthorized modifications.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000141 — 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-2017-1000141 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