dbcve.org
Web Report StudioApplication · Sas

CVE-2022-25256

MEDIUM · 6.1 CVSS v3.1 Published 2022-02-19
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
SAS Web Report Studio 4.4 allows XSS. /SASWebReportStudio/logonAndRender.do has two parameters: saspfs_request_backlabel_list and saspfs_request_backurl_list. The first one affects the content of the button placed in the top left. The second affects the page to which the user is directed after pressing the button, e.g., a malicious web page. In addition, the second parameter executes JavaScript, which means XSS is possible by adding a javascript: URL.

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

SAS Web Report Studio 4.4 contains a reflected XSS vulnerability in the /SASWebReportStudio/logonAndRender.do endpoint. The saspfs_request_backurl_list parameter allows injection of javascript: URLs, enabling arbitrary JavaScript execution in the user's browser context. The saspfs_request_backlabel_list parameter also reflects input into button content without proper sanitization.

MitigationImplement strict input validation and output encoding on both vulnerable parameters to prevent script injection. Consider applying vendor patches if available and validating all user-supplied input in this endpoint.

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 Report StudioApplication
Affected:= 4.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
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. Verify SAS Web Report Studio version is 4.4
    Check the installed SAS Web Report Studio version through the SAS Management Console or by reviewing the SAS deployment metadata. The version is typically found in the SAS InstallMeta or in the manifest file within the SASHome directory.
    Affected if The installed version is exactly 4.4 (this CVE affects only version 4.4, not other versions)
  2. Confirm the vulnerable endpoint exists
    Verify the application exposes the /SASWebReportStudio/logonAndRender.do endpoint by attempting to access it via the web browser or by checking the web server configuration for deployed SAS Web Report Studio applications.
    Affected if The /SASWebReportStudio/logonAndRender.do endpoint is accessible and responds to requests
  3. Check if SAS Web Report Studio web application is running
    Review the SAS Web Report Studio deployment status in the SAS Web Server or application server (e.g., SAS Web Infrastructure Platform). Confirm the web application is deployed and accessible via HTTP/HTTPS.
    Affected if The SAS Web Report Studio web application is deployed and running
  4. Identify external exposure of the vulnerable endpoint
    Review network accessibility of the SAS Web Report Studio interface. Check firewall rules, reverse proxy configurations, or load balancer settings to determine if the /SASWebReportStudio/logonAndRender.do endpoint is reachable from untrusted networks.
    Affected if The endpoint is externally accessible without proper network segmentation or authentication barriers

You are affected if SAS Web Report Studio version 4.4 is installed and the /SASWebReportStudio/logonAndRender.do endpoint is accessible in your environment.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and output encoding on both vulnerable parameters to prevent script injection. Consider applying vendor patches if available and validating all user-supplied input in this endpoint.

Fix this in Web Report Studio 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-2022-25256 — 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-2022-25256 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