CVE-2024-25859
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 · uneditedA path traversal vulnerability in the /path/to/uploads/ directory of Blesta before v5.9.2 allows attackers to takeover user accounts and execute arbitrary code.
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 confidenceA path traversal vulnerability exists in the /path/to/uploads/ directory of Blesta before version 5.9.2, allowing attackers to escape the intended upload directory and write files to arbitrary locations. This enables account takeover through overwriting configuration files or executable code execution via malicious file uploads.
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< 5.9.2CVSS 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
- Adjacent
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
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 Blesta installationSearch for Blesta files or check common installation paths (e.g., /var/www/html/, /home/*/public_html/, or the web root). Look for index.php or config.php files with 'blesta' references.Affected if Blesta is installed on the system
-
Determine installed Blesta versionCheck the version file or configuration. Common locations include a version.php file, composer.json, or the admin interface footer. Compare the version number to 5.9.2.Affected if Installed version is earlier than 5.9.2
-
Verify uploads directory exists and is web-accessibleLocate the /path/to/uploads/ directory within the Blesta installation. Confirm it is accessible via HTTP/HTTPS requests to the web server.Affected if The uploads directory exists and is web-accessible
-
Check if file upload functionality is enabledReview Blesta configuration settings (config.php or admin panel settings) to confirm file upload features are enabled for users.Affected if File upload functionality is enabled in Blesta settings
A system is affected if Blesta version is earlier than 5.9.2 AND the uploads directory is accessible with file upload features enabled.
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 · scoped5.9.2
Upgrade to Blesta v5.9.2 or later to remediate the path traversal vulnerability in the uploads directory.
Blesta v5.9.2
- Upgrade Blesta to version 5.9.2 or later to resolve the path traversal vulnerability
- Refer to Blesta's official upgrade documentation at www.blesta.com for detailed upgrade instructions
- After upgrading, verify that the /path/to/uploads/ directory properly restricts path traversal attempts
- Test that file upload functionality works correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2024-25859 — 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-2024-25859 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