Security readout for executives and security teams
Plain-English summary
STVS ProVision contains a reflected cross-site scripting issue in the POST parameter named files. An authenticated attacker could cause script or HTML content to run in another user's browser session if that user interacts with a crafted request or page flow. The bundle does not show CISA KEV listing or active exploitation evidence.
Executive priority
Treat as a medium-priority remediation item. Prioritize faster if the affected ProVision instance is internet-facing, used by privileged staff, or lacks strong access controls.
Technical view
CVE-2021-47725 is a CWE-79 reflected XSS vulnerability affecting STVS ProVision, including versions 5.9.10, 5.9.9, 5.9.7, 5.9.1, 5.9.0, 5.8.6, 5.7, 5.6, and 5.5. The reported vulnerable input is the files POST parameter. CVSS v3.1 is 5.4 with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, meaning network reachable, low complexity, low privileges required, user interaction required, changed scope, and limited confidentiality/integrity impact.
Likely exposure
Organizations running the listed STVS ProVision versions may be exposed where authenticated users can reach the vulnerable function. Exposure is higher if the application is reachable by many users or externally accessible, but the source bundle does not establish internet-wide exposure.
Exploitation context
The bundle includes third-party advisory references and an exploit-labeled Packet Storm entry, indicating public technical disclosure/exploit information exists. CISA KEV is false, and no provided source in the bundle states active exploitation in the wild.
Researcher notes
Do not treat this as confirmed active exploitation based on the supplied data. The strongest risk signals are authenticated reflected XSS, public advisory coverage, and an exploit-labeled reference. Patch status is not established in the bundle, so remediation should be anchored to current STVS guidance.
Mitigation direction
- Check STVS vendor guidance for a fixed version or official remediation, because the bundle does not include patch or fixed-version evidence.
- Upgrade or apply vendor-provided patches if STVS confirms a corrected release.
- Restrict access to affected STVS ProVision interfaces to trusted networks and necessary authenticated users only.
- Validate and constrain the files parameter server-side, and ensure user-controlled output is contextually encoded before rendering in HTML responses.
- Review session handling and administrative workflows to reduce the impact of authenticated reflected XSS, especially for privileged users.
Validation and detection
- Inventory STVS ProVision deployments and compare versions against the affected version list in the bundle.
- Confirm whether the files POST parameter is reachable by authenticated users in deployed instances.
- In an authorized test environment, verify that HTML-like input submitted through the files parameter is rejected, neutralized, or rendered as text rather than interpreted by the browser.
- After applying vendor remediation or compensating controls, repeat the same benign validation and review logs for rejected malformed input.
- Document whether public or broad internal access exists, since exposure level depends heavily on deployment placement and user population.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-47725 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N2.32.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- Zero Science Lab Disclosure (ZSL-2021-5624)CVE reference · third-party-advisory
- Packet Storm Security Exploit EntryCVE reference · exploit
- CXSecurity Vulnerability ListingCVE reference · third-party-advisory
- IBM X-Force Vulnerability ExchangeCVE reference · vdb-entry
- Vendor HomepageCVE reference · product
- VulnCheck Advisory: STVS ProVision 5.9.10 Authenticated Reflected Cross-Site Scripting via Files ParameterCVE reference · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.