dbcve.org
Luxcal Web CalendarApplication · Luxsoft

CVE-2025-25222

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 retrieve.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

SQL injection vulnerability in retrieve.php of LuxCal Web Calendar versions prior to 5.3.3M (MySQL) and 5.3.3L (SQLite). The vulnerability allows unauthenticated attackers to manipulate SQL queries, potentially enabling deletion, alteration, or exfiltration of database contents.

MitigationUpgrade to LuxCal Web Calendar version 5.3.3M (MySQL) or 5.3.3L (SQLite) or later to remediate the SQL injection vulnerability.

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. Locate the LuxCal retrieve.php file
    Search the web server document root for the file 'retrieve.php' which contains the vulnerable SQL query logic. Common paths may include /luxcal/ or /calendar/ subdirectories.
    Affected if The file retrieve.php exists in the web accessible directory and the LuxCal version is below 5.3.3L or 5.3.3M depending on database type.
  2. Identify the LuxCal version
    Open retrieve.php or check for a version indicator file within the LuxCal installation directory. Look for a version constant, changelog, or config file that displays the current software version.
    Affected if The installed version is less than 5.3.3L for SQLite databases or less than 5.3.3M for MySQL databases.
  3. Confirm the database type in use
    Check the LuxCal configuration file (such as 'database.php' or similar) to determine whether MySQL or SQLite is the active database backend.
    Affected if Using SQLite with version < 5.3.3L or MySQL with version < 5.3.3M.
  4. Verify retrieve.php is web-accessible
    Attempt to access retrieve.php via HTTP/HTTPS to confirm it is publicly reachable without authentication.
    Affected if retrieve.php responds to web requests and the version is vulnerable.

A user is affected if LuxCal Web Calendar is installed with retrieve.php accessible and the installed version is below 5.3.3L (SQLite) or below 5.3.3M (MySQL).

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 to remediate the SQL injection vulnerability.

Recommended fix High confidence

5.3.3L (SQLite) or 5.3.3M (MySQL)

  1. 1. Identify which database backend your LuxCal Web Calendar uses (MySQL or SQLite)
  2. 2. For SQLite users: Download version 5.3.3L from www.luxsoft.eu
  3. 3. For MySQL users: Download version 5.3.3M from www.luxsoft.eu
  4. 4. Create a complete backup of your current calendar installation including the database
  5. 5. Replace the existing LuxCal files with the files from the downloaded fixed version, or at minimum replace retrieve.php with the patched version
  6. 6. Verify the calendar functions correctly after the update

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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