CVE-2021-45915
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 · uneditedIn LuxSoft LuxCal Web Calendar before 5.2.0, an unauthenticated attacker can manipulate a cookie value. 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 confidenceLuxSoft LuxCal Web Calendar before 5.2.0 contains an authentication bypass vulnerability where unauthenticated attackers can manipulate cookie values to impersonate any registered user, including administrators. This allows complete unauthorized access to the application with privileged credentials.
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< 5.2.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate LuxCal installationSearch web server directories for LuxCal calendar application files (common paths include /luxcal, /calendar, or /webcal). Check for the presence of index.php, or the main LuxCal PHP files.Affected if LuxCal Web Calendar is found on the system
-
Identify installed versionLocate the version information file or check the main LuxCal PHP files for a version string. Common locations include a dedicated version file, the footer of the web interface, or the header/include files.Affected if Version cannot be determined or is below 5.2.0
-
Verify cookie-based authentication is in useExamine the login process by attempting to authenticate and capturing the HTTP response headers and cookies. Check if the application sets authentication cookies (such as a session cookie or user ID cookie) upon login.Affected if The application uses cookies to maintain authenticated sessions
-
Confirm vulnerability conditionCompare your confirmed installed version against the affected range: versions prior to 5.2.0 are vulnerable to the authentication bypass via cookie manipulation.Affected if Installed version is less than 5.2.0 and cookie-based authentication is active
If LuxCal Web Calendar is installed with a version below 5.2.0 and uses cookie-based authentication, the environment is affected by this authentication bypass vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.2.0
Upgrade LuxCal Web Calendar to version 5.2.0 or later to remediate the cookie manipulation vulnerability. If immediate patching is not possible, consider restricting access to the calendar application via network-level controls until the upgrade can be applied.
LuxCal 5.2.0 or later
- Back up the current LuxCal installation and database before proceeding with the upgrade
- Download LuxCal version 5.2.0 or later from the official source at www.luxsoft.eu or the official GitHub repository
- Extract the downloaded archive and replace all existing LuxCal files with the new version
- Ensure the config file (lcconfig.php) is preserved or updated to match the new version requirements
- Verify the upgrade was successful by accessing the calendar and checking the version number
- Test authentication to confirm the cookie-based session vulnerability has been remediated
- Review any new features or changes in version 5.2.0 that may affect calendar users
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45915 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-45915 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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