CVE-2023-47175
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 · uneditedCross-site scripting 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 script on the web browser of the user who is accessing the product.
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 confidenceCross-site scripting (XSS) vulnerability in LuxCal Web Calendar versions prior to 5.2.4M (MySQL) and 5.2.4L (SQLite) allows remote unauthenticated attackers to inject and execute arbitrary JavaScript or other scripts in the context of a user's browser when they access the calendar application.
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.4l< 5.2.4mCVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 the LuxCal Web Calendar versionCheck the version file or header in the LuxCal installation. Common locations include a version.php file, the config.php file, or the application's about/footer page. The version string typically appears as something like '5.2.3' or similar.Affected if The version cannot be determined or is lower than 5.2.4L (for SQLite) or lower than 5.2.4M (for MySQL)
-
Determine the database type in useInspect the LuxCal configuration file (config.php or settings.php) to identify whether the installation uses MySQL or SQLite database. Look for database connection parameters or a reference to a .sqlite file.Affected if The database type is MySQL and version is below 5.2.4M, or SQLite and version is below 5.2.4L
-
Verify the application is network accessibleConfirm that the LuxCal Web Calendar is accessible over HTTP/HTTPS to remote users. This can be done by accessing the calendar URL from a browser or using a curl command to the application's main page.Affected if The calendar is publicly accessible and the version is unpatched, meaning the XSS can be triggered by any remote user
A user is affected if their LuxCal Web Calendar installation version is below 5.2.4L (for SQLite) or below 5.2.4M (for MySQL) and the application is accessible to remote users.
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.4l5.2.4m
Upgrade LuxCal Web Calendar to version 5.2.4M (MySQL) or 5.2.4L (SQLite) or later to obtain the patched version with proper input sanitization and output encoding.
LuxCal Web Calendar 5.2.4M (MySQL) or 5.2.4L (SQLite)
- 1. Identify which database backend your LuxCal Web Calendar installation uses (MySQL or SQLite)
- 2. For MySQL installations: Download and install LuxCal Web Calendar version 5.2.4M or later from the official vendor site (www.luxsoft.eu)
- 3. For SQLite installations: Download and install LuxCal Web Calendar version 5.2.4L or later from the official vendor site (www.luxsoft.eu)
- 4. Replace all existing calendar files with the new version files, preserving your configuration and database
- 5. Verify the upgrade was successful by accessing the calendar interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47175 — 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-2023-47175 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