dbcve.org
Luxcal Web CalendarApplication · Luxsoft

CVE-2025-25221

CRITICAL · 9.8 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 →
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
The LuxCal Web Calendar prior to 5.3.3M (MySQL version) and prior to 5.3.3L (SQLite version) contains an SQL injection vulnerability in pdf.php. If this vulnerability is exploited, information in a database may be deleted, altered, or retrieved.

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

The LuxCal Web Calendar contains a critical SQL injection vulnerability in the pdf.php file affecting versions prior to 5.3.3M for MySQL and 5.3.3L for SQLite. This allows unauthenticated attackers to manipulate database queries, potentially enabling data exfiltration, modification, or deletion.

MitigationUpgrade to LuxCal Web Calendar version 5.3.3M (MySQL) or 5.3.3L (SQLite) or later. Until patched, restrict access to pdf.php via web server configuration or implement WAF rules to block suspicious SQL-like patterns in requests.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 checks

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

  1. Identify LuxCal Web Calendar installed version
    Locate the version file or check the main index page footer for the version number. Common locations include a 'version.php' file in the installation directory or the footer of the calendar homepage.
    Affected if Version is below 5.3.3l (for SQLite) or below 5.3.3m (for MySQL)
  2. Verify pdf.php exists in the web root
    Check for the presence of the file 'pdf.php' in the LuxCal installation directory accessible via the web server.
    Affected if The file pdf.php exists and is web-accessible
  3. Confirm database type in use
    Examine the LuxCal configuration file (typically 'lcconfig.php' or similar) to determine whether the calendar uses MySQL or SQLite as its backend database.
    Affected if Database is MySQL (check for version < 5.3.3m) or SQLite (check for version < 5.3.3l)
  4. Check for unauthenticated access to pdf.php
    Attempt a direct HTTP request to pdf.php without authentication credentials. If the script executes without requiring login, the SQL injection vector is exposed.
    Affected if pdf.php executes without authentication and processes parameters

A user is affected if their LuxCal Web Calendar installation is version 5.3.3L or lower for SQLite (or 5.3.3M or lower for MySQL) and the pdf.php file is accessible without authentication.

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 (MySQL) or 5.3.3L (SQLite) or later. Until patched, restrict access to pdf.php via web server configuration or implement WAF rules to block suspicious SQL-like patterns in requests.

Recommended fix Moderate confidence

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

  1. 1. Backup your current LuxCal Web Calendar installation and database before proceeding with the upgrade
  2. 2. Download the appropriate fixed version of LuxCal Web Calendar from the official vendor (www.luxsoft.eu): version 5.3.3L for SQLite or version 5.3.3M for MySQL
  3. 3. Replace the existing LuxCal installation files with the new version, preserving your configuration and data files
  4. 4. Verify the pdf.php file has been updated to the fixed version
  5. 5. Test the calendar application to ensure functionality is intact
  6. 6. Confirm the SQL injection vulnerability is remediated by verifying the pdf.php parameter handling

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

Fix this in Luxcal Web Calendar Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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