dbcve.org
Web Administration InterfaceApplication · Sas

CVE-2023-24724

MEDIUM · 5.4 CVSS v3.1 Published 2023-04-03
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

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
A stored cross site scripting (XSS) vulnerability was discovered in the user management module of the SAS 9.4 Admin Console, due to insufficient validation and sanitization of data input into the user creation and editing form fields. The product name is SAS Web Administration interface (SASAdmin). For the product release, the reported version is 9.4_M2 and the fixed version is 9.4_M3. For the SAS release, the reported version is 9.4 TS1M2 and the fixed version is 9.4 TS1M3.

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

A stored cross-site scripting (XSS) vulnerability exists in SAS 9.4 Admin Console's user management module. Due to insufficient input validation and sanitization, malicious JavaScript can be injected through user creation and editing form fields, allowing the script to execute when other users view the affected user records.

MitigationApply the vendor patch by upgrading from SAS 9.4_M2/9.4 TS1M2 to version 9.4_M3/9.4 TS1M3 or later to remediate the stored XSS vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Web Administration InterfaceApplication
Affected:= 9.4

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
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify SAS Web Administration Interface installation
    Locate the SAS installation directory and check for the Web Administration Console component. Look for files or services related to SAS Web Administration (typically found in the SASHome directory under WebAdministration or similar paths).
    Affected if The SAS Web Administration Interface version 9.4 is installed and running.
  2. Determine the exact SAS 9.4 version
    Access the SAS Web Administration Console. The version information is usually available in the console's About or System Information page, or check the SAS deployment data (SASV9.cfg file or SAS Installation Data files). Compare against 9.4_M2/9.4 TS1M2 and 9.4_M3/9.4 TS1M3.
    Affected if The version is 9.4_M2 or 9.4 TS1M2 (or earlier). Versions 9.4_M3/9.4 TS1M3 and later are not affected.
  3. Verify user management module access
    Log in to the SAS Web Administration Console and navigate to the User Management or User Administration section. Confirm that you have access to create, edit, or view user records.
    Affected if The user management module is accessible and you can view user records.
  4. Inspect user records for injected scripts
    In the User Management module, examine existing user account records. Review fields such as Display Name, Full Name, Email, Description, or any custom fields for suspicious patterns like <script>, javascript:, onerror=, or other HTML/JavaScript code.
    Affected if Any user record fields contain unescaped HTML or JavaScript code that could execute in a browser.

A user is affected if they are running SAS Web Administration Interface version 9.4_M2 or 9.4 TS1M2 (or earlier) and can access the user management module where malicious script content may already be stored in user records.

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 vendor patch by upgrading from SAS 9.4_M2/9.4 TS1M2 to version 9.4_M3/9.4 TS1M3 or later to remediate the stored XSS vulnerability.

Recommended fix High confidence

9.4_M3 (also referenced as 9.4 TS1M3)

  1. Identify the current SAS Web Administration Interface version (confirm it is 9.4_M2 or 9.4 TS1M2)
  2. Obtain the SAS 9.4_M3 (or 9.4 TS1M3) update package from SAS support
  3. Back up the current SAS Web Administration Interface configuration and database
  4. Apply the upgrade following SAS official upgrade documentation for the Web Administration Interface
  5. Restart the SAS Web Administration Interface services after upgrade
  6. Verify the upgrade was successful by checking the version number
  7. Log in to the SAS Web Administration Console and navigate to the user management module
  8. Create a new user or edit an existing user to confirm the XSS vulnerability is remediated

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

Fix this in Web Administration Interface Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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