CVE-2025-29992
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 · uneditedMahara before 24.04.9 exposes database connection information if the database becomes unreachable, e.g., due to the database server being temporarily down or too busy.
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 version 24.04.9 contains an information disclosure vulnerability where database connection credentials (usernames, passwords, hostnames) are exposed in error messages when the database becomes unreachable due to server downtime or overload.
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< 24.04.9CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Mahara versionCheck the version.php file in the Mahara root directory (htdocs/version.php) or look at the admin interface dashboard for the version numberAffected if The installed version is lower than 24.04.9 (e.g., 24.04.8, 24.04.0, older releases)
-
Verify error logging is enabledCheck the config.php file (htdocs/config.php) for $cfg->loglevels or verify debug mode settings. Also check if error_log or syslog is configured in PHP and MaharaAffected if Debug mode or detailed error logging is enabled, which would allow credential-containing error messages to be written to logs
-
Inspect application error logs for leaked credentialsExamine Mahara error log files (typically in data/log/ directory) and PHP error logs for entries containing database connection failures. Search for patterns like 'database', 'connection', 'failed', 'username', 'password'Affected if Any database error logs exist that contain raw database usernames, passwords, or hostnames in plain text
-
Verify database connectivity is stableTest database connection using Mahara's built-in diagnostics or by attempting to access the site. Check database server status and network connectivity between web and database serversAffected if The database server becomes unreachable or experiences connectivity issues, triggering the vulnerable error handling code
A user is affected if Mahara version is below 24.04.9 and the application has logged database connection errors containing plaintext credentials, or if the database is prone to connectivity issues where such exposure could occur.
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.
dbcve · scoped24.04.9
Upgrade to Mahara 24.04.9 or later to receive the patch. Until upgrade is possible, ensure database servers remain available and monitor for leaked credentials in application logs.
24.04.9
- Upgrade Mahara to version 24.04.9 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29992 — 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-2025-29992 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