CVE-2024-47097
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 Follet School Solutions Destiny before v22.0.1 AU1 allows a remote attacker to run arbitrary client-side code via the site parameter of handleloginform.do.
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 confidenceA stored Cross Site Scripting vulnerability exists in Follett School Solutions Destiny before v22.0.1 AU1. The site parameter of the handleloginform.do endpoint does not properly sanitize user input, allowing a remote attacker to inject malicious JavaScript code that executes in the victim's browser when the parameter is reflected in the response.
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
- Authentication
- X
- User interaction
- A
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 Destiny product and versionAccess the Destiny admin interface or check the software inventory. The version is typically displayed on the login page footer or in the About section of the admin dashboard.Affected if The installed version is Follett Destiny prior to v22.0.1 AU1
-
Verify handleloginform.do endpoint existsAttempt to access the handleloginform.do endpoint via the web browser (e.g., https://[hostname]/handleloginform.do or check if it's a valid route in the application's URL structure).Affected if The endpoint is accessible and responds to requests
-
Check application logs for site parameter usageReview web server or application logs for requests to handleloginform.do that contain the 'site' parameter. Look for unusual or encoded characters in the parameter value.Affected if Logs show the site parameter is being processed without sanitization or contains suspicious input patterns
-
Inspect login form source for unsanitized reflectionAccess the login page and view the HTML source. Submit a test value to the site parameter (e.g., via URL parameter) and inspect if the value appears unchanged in the response without HTML encoding.Affected if The site parameter value is reflected in the response without proper HTML encoding (e.g., <script> tags appear as literal text vs. escaped)
You are affected if Follett Destiny v22.0.1 AU1 or earlier is installed AND the handleloginform.do endpoint processes the site parameter 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.
dbcve · scopedUpdate to Destiny v22.0.1 AU1 or later, which contains the patch for this vulnerability. If immediate patching is not possible, implement input validation and output encoding for the site parameter on the handleloginform.do endpoint.
v22.0.1 AU1 (or later stable release)
- 1. Verify current Follet School Solutions Destiny version by accessing the admin console or checking system information
- 2. Download Follet School Solutions Destiny v22.0.1 AU1 or later from the official Follett portal
- 3. Back up the current Destiny database and configuration files
- 4. Follow Follett's official upgrade documentation to install v22.0.1 AU1
- 5. After upgrade, verify the handleloginform.do endpoint is no longer vulnerable by testing with a benign XSS payload in the site parameter
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47097 — 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-47097 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