CVE-2024-51635
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 Request Forgery (CSRF) vulnerability in Garmur While Loading while-it-is-loading allows Stored XSS.This issue affects While Loading: from n/a through <= 3.0.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in Garmur's 'While Loading' component allows attackers to inject malicious scripts (Stored XSS) by tricking authenticated administrators into visiting crafted pages. The lack of CSRF protection on state-changing operations enables the attack, and the injected payload persists for all users encountering the loading screen.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm Garmur installationIdentify if Garmur software is present in your environment by checking installed packages, software inventories, or the application itselfAffected if Garmur is not installed on the system
-
Locate the While Loading componentAccess the Garmur admin interface or configuration files and navigate to find the 'While Loading' component or feature settingsAffected if The While Loading component exists and is accessible in the application
-
Verify admin authentication requirementCheck if configuration changes to the While Loading component require authenticated administrator sessionsAffected if State-changing operations on While Loading can be performed without requiring valid admin authentication tokens or sessions
-
Inspect While Loading configuration storageExamine the database, configuration file, or backend storage where While Loading settings are persisted. Look for any script tags, javascript: URIs, or HTML event attributes in the stored valuesAffected if The stored configuration contains unsanitized or encoded malicious script content that could execute
-
Test loading screen renderingLoad the While Loading screen in a browser and view page source or use developer tools to inspect how the configured content is renderedAffected if The rendered output executes injected JavaScript or displays HTML without proper output encoding
You are affected if Garmur with the While Loading component is installed AND unauthenticated or easily tricked administrators can modify the configuration AND malicious scripts are stored and rendered without sanitization.
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 dataImplement anti-CSRF tokens (synchronizer token pattern) on all forms and AJAX endpoints that modify the 'While Loading' configuration, combined with proper output encoding to prevent XSS when the content is rendered.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51635 — 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-51635 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