dbcve.org
CraftercmsApplication

CVE-2025-0502

CRITICAL · 9.1 CVSS v3.1 Published 2025-01-15
Fix available
A fix is available. Upgrade to 4.0.8 / 4.1.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Transmission of Private Resources into a New Sphere ('Resource Leak') vulnerability in CrafterCMS Engine on Linux, MacOS, x86, Windows, 64 bit, ARM allows Directory Indexing, Resource Leak Exposure.This issue affects CrafterCMS: from 4.0.0 before 4.0.8, from 4.1.0 before 4.1.6.

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 confidence

A resource leak vulnerability in CrafterCMS Engine allows unauthorized directory indexing and exposure of private resources. The flaw exists in versions 4.0.0 through 4.0.7 and 4.1.0 through 4.1.5, where improper resource management during request handling can leak internal files and enable directory traversal.

MitigationUpgrade CrafterCMS Engine to version 4.0.8, 4.1.6, or later to patch the resource leak. Review and restrict filesystem access permissions as a defense-in-depth measure while planning the upgrade.

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
CraftercmsApplication
Affected:>= 4.0.0, < 4.0.8>= 4.1.0, < 4.1.6

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
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed CrafterCMS Engine version
    Locate the CrafterCMS Engine version from the deployed WAR file, startup logs, or administrative console. Common locations include the MANIFEST.MF file in the engine WAR or the about/version page in the admin panel.
    Affected if The installed version is 4.0.0 through 4.0.7, or 4.1.0 through 4.1.5 (falls within the affected ranges).
  2. Verify directory indexing configuration
    Inspect the web server or servlet container configuration (such as Tomcat's server.xml or web.xml) for directory listing settings. Check if directory listing is explicitly enabled for any web application paths.
    Affected if Directory indexing is enabled on paths serving CrafterCMS Engine content.
  3. Check static resource handling configuration
    Review CrafterCMS configuration files that control static resource serving. Look for settings that determine whether private or internal resources are accessible without authentication.
    Affected if Static resource configuration allows unauthenticated access to files that should be restricted.
  4. Audit publicly accessible paths
    Probe the deployed CrafterCMS Engine instance by requesting common directory paths (such as /static-assets/, /media/, or root-level paths) to observe if directory listings or file contents are returned when they should not be.
    Affected if Directory listings display or unauthorized files are returned when accessing paths that should require authentication.

A user is affected if CrafterCMS Engine version is below 4.0.8 or 4.1.6 AND directory indexing or unrestricted static resource access is enabled in the configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.0.8 / 4.1.6 or later
Fixed in 4.0.84.1.6
Interim mitigation

Upgrade CrafterCMS Engine to version 4.0.8, 4.1.6, or later to patch the resource leak. Review and restrict filesystem access permissions as a defense-in-depth measure while planning the upgrade.

Recommended fix High confidence

CrafterCMS 4.0.8 or 4.1.6 (depending on your major version branch)

  1. Identify your current CrafterCMS version (4.0.x or 4.1.x) by checking the version manifest or startup logs
  2. Backup your CrafterCMS data directory and database before proceeding with any upgrade
  3. Stop the CrafterCMS Engine service
  4. If running 4.0.x: upgrade to CrafterCMS 4.0.8; if running 4.1.x: upgrade to CrafterCMS 4.1.6
  5. Replace the CrafterCMS Engine installation files with the corresponding fixed version
  6. Start the CrafterCMS Engine service
  7. Verify the application starts successfully and test that static resource access is properly restricted
  8. Review CrafterCMS release notes for the target version for any additional configuration requirements
Caveat Review the 4.0.8 and 4.1.6 release notes for any breaking changes or configuration updates required for your specific deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Craftercms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0502 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0502 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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