dbcve.org
LuxcalApplication · Luxsoft

CVE-2021-45914

CRITICAL · 9.8 CVSS v3.1 Published 2022-05-24
Fix available
A fix is available. Upgrade to 5.2.0 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
In LuxSoft LuxCal Web Calendar before 5.2.0, an unauthenticated attacker can manipulate a POST request. This allows the attacker's session to be authenticated as any registered LuxCal user, including the site administrator.

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

In LuxSoft LuxCal Web Calendar before version 5.2.0, an unauthenticated attacker can manipulate a POST request to have their session authenticated as any registered user, including the administrator account. This is a pre-authentication bypass that enables full account takeover without knowing any valid credentials.

MitigationUpgrade LuxCal Web Calendar to version 5.2.0 or later, which contains the vendor fix for this authentication bypass 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
LuxcalApplication
Affected:< 5.2.0

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 LuxCal Web Calendar installation
    Identify the web server directory where LuxCal calendar application is installed. Common paths include /luxcal, /calendar, or the web root. Check web server configuration files or perform web enumeration to find the application.
    Affected if LuxCal Web Calendar is installed on the server
  2. Determine installed LuxCal version
    Access the LuxCal about page, typically found at /about.php or check the footer of any LuxCal page for the version number. Alternatively, examine the main configuration file (common names include config.php or settings.php) for a version string.
    Affected if The version displayed or stored in configuration files is below 5.2.0 (e.g., 5.1.x, 5.0.x, 4.x)
  3. Verify POST authentication endpoints are accessible
    Test that the LuxCal login form accepts POST requests to the authentication handler (typically the root index.php or a dedicated auth endpoint). Confirm the application processes user credentials via HTTP POST method.
    Affected if The application processes POST-based login requests, indicating the vulnerable authentication mechanism is in use
  4. Confirm user database contains registered accounts
    Check if the LuxCal database or user configuration contains registered user accounts, particularly an administrator account. The vulnerability allows impersonation of any existing user.
    Affected if Registered user accounts exist in the system (including administrator)
  5. Compare installed version against affected range
    Review the identified version number and compare it to the affected range: any version less than 5.2.0. Document the exact version for vulnerability assessment records.
    Affected if Installed version is 5.1.9, 5.1.8, 5.1.7, 5.1.6, 5.1.5, 5.1.4, 5.1.3, 5.1.2, 5.1.1, 5.1.0, or any earlier version

The environment is affected if LuxCal Web Calendar is installed and the running version is any release prior to 5.2.0, as the pre-authentication bypass allows unauthorized session hijacking of any registered user account.

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.0 or later
Fixed in 5.2.0
Interim mitigation

Upgrade LuxCal Web Calendar to version 5.2.0 or later, which contains the vendor fix for this authentication bypass vulnerability.

Recommended fix High confidence

LuxCal 5.2.0

  1. Backup the current LuxCal installation and database before making any changes
  2. Navigate to the official LuxSoft download page at www.luxsoft.eu
  3. Download LuxCal version 5.2.0 or later
  4. Extract the new version and replace the existing LuxCal files on the server
  5. Run any provided upgrade script if included in the release
  6. Log in to the admin panel and verify the calendar functions correctly
  7. Check user accounts for any unauthorized admin accounts that may have been created by attackers
  8. Review server logs for signs of exploitation attempts

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

Fix this in Luxcal 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-2021-45914 — 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-2021-45914 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