dbcve.org
Luxcal Web CalendarApplication · Luxsoft

CVE-2023-46700

CRITICAL · 9.8 CVSS v3.1 Published 2023-11-20
Fix available
A fix is available. Upgrade to 5.2.4l / 5.2.4m 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
SQL injection vulnerability in LuxCal Web Calendar prior to 5.2.4M (MySQL version) and LuxCal Web Calendar prior to 5.2.4L (SQLite version) allows a remote unauthenticated attacker to execute an arbitrary SQL command by sending a crafted request, and obtain or alter information stored in the database.

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 LuxCal Web Calendar allows remote unauthenticated attackers to execute arbitrary SQL commands via crafted requests, potentially exposing or modifying database contents.

MitigationUpdate LuxCal Web Calendar to version 5.2.4M (MySQL) or 5.2.4L (SQLite) or later. If immediate patching is not possible, restrict network access to the calendar application and implement WAF rules to filter malicious SQL-like payloads.

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.2.4l< 5.2.4m

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 installation and version
    Check the file 'lcdefs.php' in the LuxCal root directory for the $cfVersion variable, or check the admin interface Dashboard page for the version number
    Affected if The version shown is below 5.2.4L (for SQLite) or below 5.2.4M (for MySQL)
  2. Determine database backend type
    Inspect the 'lcdefs.php' file for the database configuration. Look for $cfDbType variable - values typically include 'sqlite' or 'mysql'/'mysqli'
    Affected if The application uses either SQLite or MySQL backend with a version below the fixed releases
  3. Check for unauthenticated access exposure
    Review web server configuration or firewall rules to determine if the calendar application is accessible from untrusted networks (internet or DMZ)
    Affected if The LuxCal application is directly accessible from the internet without authentication requirements
  4. Examine application logs for SQL injection attempts
    Review web server access logs (Apache/nginx) and LuxCal's own logs in the 'logs/' directory for suspicious SQL-like patterns (e.g., UNION SELECT, OR 1=1, quotes in unusual places)
    Affected if Log entries show SQL injection payloads targeting calendar parameters or forms
  5. Check database for unauthorized modifications
    Query the database for unexpected users, modified settings, or new records in administrative tables. For SQLite, examine the .db file directly; for MySQL, run SHOW TABLES and inspect key tables
    Affected if Unexpected records exist in the database, particularly in tables related to users, settings, or events, that were not created by legitimate administrators

You are affected if LuxCal Web Calendar is installed with a version below 5.2.4L (SQLite) or below 5.2.4M (MySQL) and is accessible to unauthenticated network attackers.

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

Update LuxCal Web Calendar to version 5.2.4M (MySQL) or 5.2.4L (SQLite) or later. If immediate patching is not possible, restrict network access to the calendar application and implement WAF rules to filter malicious SQL-like payloads.

Recommended fix High confidence

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

  1. 1. Identify which database type (MySQL or SQLite) your LuxCal Web Calendar installation uses
  2. 2. If using MySQL, upgrade to version 5.2.4M or later
  3. 3. If using SQLite, upgrade to version 5.2.4L or later
  4. 4. Verify the upgrade was successful by checking the calendar version in the admin interface
  5. 5. Test that the application functions normally after the upgrade

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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