Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NSummary
CVE-2022-30690 is a medium-severity Cross-site Scripting (CWE-79) vulnerability in Wwbn Avideo. Its CVSS base score is 6.1 (Medium).
Operationally, ranked in the top 0.3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-15 (Information Output Filtering) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
A cross-site scripting vulnerability tracked as CVE-2022-30690 affects the image403 functionality in WWBN AVideo version 11.6 and the development master commit 3f7c0364. The flaw, assigned CWE-79, permits arbitrary JavaScript execution when a specially crafted HTTP request is processed, carrying a CVSS 3.1 score of 6.1.
An unauthenticated attacker can exploit the issue by inducing an authenticated user to submit the malicious request, resulting in JavaScript execution within the context of the victim's session. This enables limited impacts on confidentiality and integrity without requiring elevated privileges beyond social engineering the target user.
Public references point to Talos Intelligence advisory TALOS-2022-1539 for detailed analysis and to the AVideo updateDb.v12.0.sql script as the mechanism for applying remediation changes. The EPSS score rose from lower values after the 2022 disclosure to a peak of 0.1514 in December 2025 before receding to the current 0.0981, indicating a later surge in exploitation interest that warrants renewed attention.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-52520
Vulnerability Data
A cross-site scripting (xss) vulnerability exists in the image403 functionality of WWBN AVideo 11.6 and dev master commit 3f7c0364. A specially-crafted HTTP request can lead to arbitrary Javascript execution. An attacker can get an authenticated user to send a crafted…
more
HTTP request to trigger this vulnerability.
- CWE(s)
Related Threats
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly blocks the specially-crafted HTTP request from being accepted by the image403 function, preventing the malicious JavaScript payload from reaching the renderer.
Filters the crafted response content returned by image403 so that arbitrary JavaScript is stripped before it executes in the authenticated user's browser.
Boundary-protection devices such as a WAF can inspect HTTP requests to image403 and block or alert on XSS patterns matching this vulnerability.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly target introduction of XSS via coding standards/testing (mostly), yet the single broad outcome leaves many specific neutralization vectors unaddressed (partial).
Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure-coding testing and automated code-analysis tools are applied to detect improper neutralization of script-related content during web-page generation.
Knowledge exchange on emerging attack techniques and patches reduces the likelihood that cross-site scripting flaws remain unaddressed in deployed applications.
Operational indicators of compromise for web-application attacks can be incorporated into WAF or input-filtering rules, lowering the likelihood that unsanitized data reaches the browser.
Requiring language-specific secure-coding standards and automated scanning during the SDLC catches missing output encoding or improper neutralization of untrusted data before the software reaches production.
Secure-coding standards, SAST scans and removal of insecure code samples together eliminate the failure to neutralize script content that produces cross-site scripting flaws.
Webpage malware scanning and block-listing of known malicious sites reduce the likelihood that reflected or stored script payloads reach a user’s browser.