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

CVE-2026-32856

MEDIUM · 6.1 CVSS v3.1 Published 2026-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/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
Ellucian Banner Self-Service before the April T2 release (2025-04-23) contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to execute arbitrary JavaScript in a victim's browser by injecting unsanitized input through the toDateFormat request parameter in the dateConverter endpoint. Attackers can craft a malicious URL targeting the unauthenticated dateConverter endpoint to steal session cookies or perform other malicious actions in the context of the victim's browser session.

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 XSS vulnerability in Ellucian Banner Self-Service's dateConverter endpoint allows unauthenticated attackers to inject arbitrary JavaScript via the toDateFormat request parameter, enabling session cookie theft and browser-based attacks.

MitigationApply the April T2 release (2025-04-23) patch from Ellucian or implement input validation/sanitization on the toDateFormat parameter to neutralize script injection attempts.

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
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 checks

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

  1. Confirm Ellucian Banner Self-Service is exposed
    Identify web applications responding on your external or internal networks that serve Ellucian Banner Self-Service. Check HTTP response headers or the application's login page for 'Ellucian' or 'Banner' branding.
    Affected if The application is publicly or internally accessible and identifies as Ellucian Banner Self-Service.
  2. Determine the installed version
    Locate the version number of the Ellucian Banner installation. This is typically found in the admin control panel, release notes, or by inspecting the application's footer/branding area. Compare this version to the April T2 2025 release (2025-04-23).
    Affected if The installed version is earlier than the April T2 2025 release.
  3. Test the dateConverter endpoint for XSS
    Send an HTTP GET request to the dateConverter endpoint with a benign XSS payload in the toDateFormat parameter, for example: /dateConverter?toDateFormat=%3Cscript%3Ealert(1)%3C/script%3E. Inspect the HTTP response to see if the payload is reflected unmodified.
    Affected if The response returns the script tags or other HTML/JS from the parameter without encoding or sanitization.
  4. Verify the endpoint is unauthenticated
    Attempt to access the dateConverter endpoint without providing any authentication credentials or session cookies.
    Affected if The endpoint responds without requiring login, making it exploitable by unauthenticated attackers.

A user is affected if they are running any version of Ellucian Banner Self-Service earlier than the April T2 2025 release and the dateConverter endpoint reflects unsanitized input from the toDateFormat parameter without authentication.

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

Apply the April T2 release (2025-04-23) patch from Ellucian or implement input validation/sanitization on the toDateFormat parameter to neutralize script injection attempts.

Recommended fix Moderate confidence

Ellucian Banner Self-Service April T2 release (2025-04-23) or later

  1. 1. Navigate to the Ellucian customer portal or contact Ellucian Support to obtain the April T2 release (2025-04-23) or later for Banner Self-Service
  2. 2. Download the security update/patch for the dateConverter endpoint XSS vulnerability
  3. 3. Follow Ellucian's standard upgrade procedures to apply the April T2 2025 release
  4. 4. After upgrading, verify the fix by testing that the toDateFormat parameter in the dateConverter endpoint properly sanitizes input and no longer reflects unsanitized JavaScript

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32856 — 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-2026-32856 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