dbcve.org
Luxcal Web CalendarApplication · Luxsoft

CVE-2025-25223

MEDIUM · 5.3 CVSS v3.1 Published 2025-02-18
Fix available
A fix is available. Upgrade to 5.3.3l / 5.3.3m or later.
See remediation →
62/100
Remediation priority · Elevated
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
The LuxCal Web Calendar prior to 5.3.3M (MySQL version) and prior to 5.3.3L (SQLite version) contains a path traversal vulnerability in dloader.php. If this vulnerability is exploited, arbitrary files on a server may be obtained.

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

LuxCal Web Calendar versions prior to 5.3.3M (MySQL) and 5.3.3L (SQLite) contain a path traversal vulnerability in dloader.php that allows attackers to read arbitrary files on the server by manipulating file path inputs with directory traversal sequences (e.g., ../../).

MitigationUpgrade to LuxCal Web Calendar version 5.3.3M or 5.3.3L (or later). If immediate patching is not possible, restrict or disable access to dloader.php via web server configuration.

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
Luxcal Web CalendarApplication
Affected:< 5.3.3l< 5.3.3m

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
Low
Integrity
None
Availability
None

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

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

  1. Locate LuxCal Web Calendar installation
    Search the web server document root for the 'luxcal' directory, or look for files named 'dloader.php' that contain 'LuxCal' or 'Luxsoft' in the source code.
    Affected if The calendar software is present on the server.
  2. Identify the installed version
    Open the file 'lcconfig.php' or 'config.php' in the LuxCal installation directory and look for a version variable, or access the calendar's main page and view the page source for version information.
    Affected if The version number found is less than 5.3.3L for SQLite or less than 5.3.3M for MySQL variants.
  3. Confirm dloader.php exists
    Check for the file 'dloader.php' within the LuxCal installation folder (commonly in the root or a 'includes' subdirectory).
    Affected if The file dloader.php exists in the LuxCal installation.
  4. Verify the file download functionality is accessible
    Attempt a simple HTTP request to the dloader.php endpoint (e.g., GET /luxcal/dloader.php) and verify the script responds (rather than returning a 404 or being blocked by the web server).
    Affected if The script is accessible via HTTP without authentication barriers.

A user is affected if LuxCal Web Calendar is installed with a version below 5.3.3L or 5.3.3M and the dloader.php file is accessible on the web server, allowing unauthenticated path traversal attacks.

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 5.3.3l / 5.3.3m or later
Fixed in 5.3.3l5.3.3m
Interim mitigation

Upgrade to LuxCal Web Calendar version 5.3.3M or 5.3.3L (or later). If immediate patching is not possible, restrict or disable access to dloader.php via web server configuration.

Recommended fix Moderate confidence

Upgrade to LuxCal Web Calendar 5.3.3L (SQLite) or 5.3.3M (MySQL)

  1. 1. Backup your current LuxCal Web Calendar installation and database before upgrading.
  2. 2. Identify your database type (MySQL or SQLite) used by your current installation.
  3. 3. Download the appropriate fixed version: version 5.3.3L for SQLite or version 5.3.3M for MySQL from the official Luxsoft.eu website.
  4. 4. Extract the downloaded package to your web server.
  5. 5. Copy the configuration file from your existing installation to the new version (typically config.php or similar).
  6. 6. Test the upgraded calendar by logging in and verifying core functionality.
  7. 7. Verify that the dloader.php file no longer allows path traversal by testing with the fixed version.

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

Fix this in Luxcal Web Calendar Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-25223 — 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-25223 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