{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-21730 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-21730 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-21730 is a medium-severity cross-site scripting vulnerability in Verint Verba, published on 14 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-21730 and fix it if it is affected.\n\nWhat it is: CVE-2026-21730 is a medium-severity cross-site scripting vulnerability in Verint Verba, published on 14 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-21730 in the wild and no public exploit code.\n\nAffected product: Verint Verba. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-21730/ (Markdown: https://insights.sbomify.com/CVE-2026-21730/index.md)","id":"CVE-2026-21730","markdown":"https://insights.sbomify.com/CVE-2026-21730/index.md","name":"CVE-2026-21730","record":{"aliases":["GHSA-pqwf-7gjw-fvph"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Verba logging application","requires_auth":"none","summary":"An attacker can inject malicious scripts via the login username field, which execute in the administrator's browser when viewing logs.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[{"product":"verba_collaboration_compliance_and_quality_management_platform","vendor":"verint"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Verba is affected by a Stored Cross-Site Scripting (XSS) vulnerability within its login logging mechanism. When an unauthenticated remote attacker attempts to log in using an incorrect username and password combination, the supplied username value is recorded in the application logs. Due to lack of input sanitization, an attacker can inject a malicious XSS payload into the username field.\nThis payload will be executed in the context of the administrator’s browser when the admin accesses the web application's log viewer.\n\nThe vendor was notified early about this vulnerability, but didn't respond to our messages. This issue was fixed in version 10.0.6","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Stored XSS in Verba","id":"CVE-2026-21730","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"GPU DDK - libusc OOB write at ConvertSwitchToArrayLookupBP during WebGPU shader compilation","id":"CVE-2026-21732"},"packages":[],"prev":{"headline":"Loki detected_fields query limits results in unbounded memory allocation","id":"CVE-2026-21729"},"products":["Verba"],"published":"2026-05-14","related":[{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2018-17871","kev_date_added":null,"published":"2018-10-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-14","vendors":["Verint"]},"summary":"An attacker can inject malicious scripts via the login username field, which execute in the administrator's browser when viewing logs.","url":"https://insights.sbomify.com/CVE-2026-21730/"}