dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2024-47096

MEDIUM · 5.1 CVSS v4.0 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Cross 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 showSupportExpiredMessage 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 confidence

Reflected Cross-Site Scripting (XSS) vulnerability in Follet School Solutions Destiny before v22.0.1 AU1 allows injection of arbitrary JavaScript through the showSupportExpiredMessage parameter of the handleloginform.do endpoint. A remote unauthenticated attacker can craft malicious URLs to execute client-side code in the context of authenticated users.

MitigationUpgrade to Destiny v22.0.1 AU1 or later to obtain the vendor patch; alternatively, implement output encoding and input validation on the affected parameter as a compensating control.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Follett Destiny product is installed
    Locate the Destiny application installation directory or check running services for 'Destiny' or 'Follett' processes. Check the product name displayed in the application UI or administrative console.
    Affected if The product is Follett School Solutions Destiny software.
  2. Determine the installed Destiny version
    Access the Destiny administrative interface and navigate to the About or System Information page, or check the version displayed on the login page footer. Alternatively, inspect the application's manifest or version file within the installation directory.
    Affected if The installed version is any version before v22.0.1 AU1 (e.g., v22.0.0, v21.x, v20.x, or earlier).
  3. Verify the handleloginform.do endpoint exists
    Attempt to access the URL path /handleloginform.do on the Destiny server (e.g., https://your-server/handleloginform.do or within the Destiny application path). Check if the endpoint responds.
    Affected if The handleloginform.do endpoint is accessible and responds to requests.
  4. Confirm the showSupportExpiredMessage parameter is processed
    Send a test request to the handleloginform.do endpoint including the parameter showSupportExpiredMessage=1 (e.g., /handleloginform.do?showSupportExpiredMessage=test) and observe if the parameter value is reflected in the response without proper encoding.
    Affected if The parameter value from showSupportExpiredMessage appears unescaped in the HTML response body.

A user is affected if Follett Destiny is installed and the version is before v22.0.1 AU1 with the handleloginform.do endpoint accessible and processing the showSupportExpiredMessage parameter without output encoding.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Destiny v22.0.1 AU1 or later to obtain the vendor patch; alternatively, implement output encoding and input validation on the affected parameter as a compensating control.

Recommended fix Moderate confidence

Follett Destiny v22.0.1 AU1

  1. Obtain the latest version of Follett School Solutions Destiny (v22.0.1 AU1 or later) from the official Follett vendor
  2. Review the official Follett upgrade documentation and release notes for v22.0.1 AU1
  3. Back up the current Destiny database and configuration files
  4. Test the upgrade in a non-production environment to verify compatibility
  5. Execute the upgrade following Follett's documented upgrade procedure
  6. Verify that the showSupportExpiredMessage parameter in handleloginform.do is now properly sanitized and no longer vulnerable to XSS
Caveat Review Follett release notes for v22.0.1 AU1 for any configuration or feature changes that may require adjustment

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47096 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-47096 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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