CVE-2024-54354
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 · uneditedMissing Authorization vulnerability in beat.k Termin-Kalender termin-kalender allows Stored XSS.This issue affects Termin-Kalender: from n/a through <= 0.99.47.
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 · moderate confidenceA stored XSS vulnerability exists in Termin-Kalender plugin due to missing authorization checks, allowing authenticated attackers to inject malicious scripts that persist and execute when other users view the affected content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
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.
-
Identify Termin-Kalender plugin versionAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate Termin-Kalender, and read the version number from the plugin descriptionAffected if The installed version is unpatched and falls within the vulnerable range (any version lacking the authorization fix)
-
Verify plugin is activeCheck that the Termin-Kalender plugin shows as 'Active' in the WordPress plugins listAffected if The plugin is installed and active, enabling the vulnerable code path to be executed
-
Check for user input formsVisit the calendar public-facing pages and identify any forms or input fields where users can submit content (event titles, descriptions, dates, locations)Affected if User input fields exist and accept content without immediate sanitization visible in the page source
-
Inspect stored content for script tagsAccess the WordPress database or plugin admin panel to view saved events; examine HTML source of calendar pages for unsanitized JavaScript tags in event fieldsAffected if Malicious script tags (<script>) or event handlers (onload, onerror, etc.) are present in stored event data and rendered in output
-
Review user role permissionsNavigate to WordPress Users > Roles or plugin settings to confirm which user roles can create/edit calendar eventsAffected if Low-privilege users (subscribers, contributors) have permission to add or modify calendar entries without admin oversight
You are affected if the Termin-Kalender plugin is active, any user role below administrator can add calendar events, and unsanitized script tags appear in stored event data or rendered HTML output.
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.
From vendor dataUpdate to a patched version of Termin-Kalender or implement proper authorization checks combined with output encoding on all user-supplied input fields.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54354 — 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-2024-54354 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