CVE-2025-58953
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 · uneditedUnauthenticated Local File Inclusion in Joly <= 1.22.0 versions.
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 confidenceUnauthenticated Local File Inclusion vulnerability in Joly CMS versions 1.22.0 and below allows remote attackers to read arbitrary files on the server via path traversal without any authentication credentials.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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 installed Joly versionLocate the Joly installation directory and check the version file, or run 'joly --version' or 'joly -v' from the command line if available. Common locations include /opt/joly, /var/www/joly, or the application's root directory where a version manifest or package.json may reside.Affected if The installed version is 1.22.0 or lower
-
Determine if web interface is accessibleCheck if the Joly web application is exposed by accessing the base URL (e.g., http://localhost:PORT or the configured hostname). Verify the service is running by checking process status with commands like 'ps aux | grep joly' or reviewing service configuration files.Affected if The web interface is reachable over the network without authentication required
-
Identify file path parameter endpointsReview application routing configuration files (such as routes.js, app.js, or similar routing definitions in the installation directory) to locate endpoints that accept file path parameters, particularly those used for file viewing, downloading, or template rendering.Affected if Endpoints accepting file path parameters exist and are accessible without authentication
-
Test for directory traversal vulnerabilitySend a crafted HTTP request to the identified file path endpoints using directory traversal sequences such as '../' or '..\' (e.g., GET /endpoint?file=../../../../etc/passwd). Use tools like curl or Burp Suite to observe whether the server returns file contents from outside the intended directory.Affected if The server returns contents of files outside the intended directory, confirming the LFI vulnerability is exploitable without authentication
A defender is affected if Joly version 1.22.0 or lower is installed, the web interface is exposed, and the directory traversal on file path parameters is exploitable without authentication.
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 dataUpgrade Joly to a version newer than 1.22.0. If no patched version is available, implement strict file access controls, validate input paths, and disable PHP execution in accessible directories.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58953 — 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-58953 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