CVE-2025-69770
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 zip slip vulnerability in the /DesignTools/SkinList.aspx endpoint of MojoPortal CMS v2.9.0.1 allows attackers to execute arbitrary commands via uploading a crafted zip file.
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 confidenceA zip slip directory traversal vulnerability exists in the /DesignTools/SkinList.aspx endpoint of MojoPortal CMS v2.9.0.1. The application fails to validate file paths within uploaded zip archives during extraction, allowing attackers to craft archives containing path traversal sequences (e.g., ../../../) to write files to arbitrary locations on the server, leading to arbitrary command execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 MojoPortal CMS versionLocate the version file or assembly info for the installed MojoPortal instance. Check the About page in the admin panel, or inspect the AssemblyInfo.cs/AssemblyVersion.cs file in the web root or bin directory.Affected if The installed version is 2.9.0.1 exactly, or if it is an earlier version that has not been patched for this traversal vulnerability.
-
Verify the DesignTools endpoint existsCheck if the path /DesignTools/SkinList.aspx is accessible on the web server. This can be done by attempting to access the URL directly via a browser or by checking the file system for the existence of SkinList.aspx in the DesignTools folder under the web root.Affected if The endpoint exists and is reachable without authentication, or with low-privilege user access.
-
Confirm skin upload feature is enabledLog into the MojoPortal administration panel and navigate to the Skin Design Tools section. Verify whether the functionality to upload or import skins from zip archives is available to the current user role.Affected if The skin upload/import feature is enabled and accessible to the user role being tested.
-
Inspect server file write permissionsCheck the file system permissions on the web root directory and subdirectories. Identify which directories are writable by the application pool identity or the account running the web server process.Affected if The web application has write permissions to directories outside the intended skins upload folder, allowing a path traversal write to succeed.
A system is affected if it runs MojoPortal CMS version 2.9.0.1 (or an unpatched earlier version), has the /DesignTools/SkinList.aspx endpoint accessible, and allows zip archive uploads through the skin management feature to directories with broader write access than intended.
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 dataImplement strict path validation on all extracted files by canonicalizing paths and verifying they fall within the intended target directory before extraction; use a secure extraction library that prevents path traversal, or validate and strip path traversal sequences from archive entries prior to extraction.
- Consultation2.0 h
- Implementation4.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 $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69770 — 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-69770 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