{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-50905 exists.","fix":"No fix has been published for CVE-2022-50905 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-50905 is a medium-severity cross-site scripting vulnerability in E107 E107, published on 13 Jan 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-2022-50905 and fix it if it is affected.\n\nWhat it is: CVE-2022-50905 is a medium-severity cross-site scripting vulnerability in E107 E107, published on 13 Jan 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-50905 exists.\n\nAffected product: E107 E107. 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-2022-50905/ (Markdown: https://insights.sbomify.com/CVE-2022-50905/index.md)","id":"CVE-2022-50905","markdown":"https://insights.sbomify.com/CVE-2022-50905/index.md","name":"CVE-2022-50905","record":{"aliases":["GHSA-7pf6-4mfj-vmpf"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"e107 CMS","requires_auth":"none","summary":"Attackers can inject malicious scripts via reflected XSS in comments or stored XSS via SVG uploads, potentially compromising user sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"e107","vendor":"e107"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"e107 CMS version 3.2.1 contains multiple vulnerabilities that allow cross-site scripting (XSS) attacks. The first vulnerability is a reflected XSS that occurs in the news comment functionality when authenticated users interact with the comment form. An attacker can inject malicious JavaScript code through the URL parameter that gets executed when users click outside the comment field after typing content. The second vulnerability involves an upload restriction bypass for authenticated administrators, allowing them to upload SVG files containing malicious code through the media manager's remote URL upload feature. This results in stored XSS when the uploaded SVG files are accessed. These vulnerabilities were discovered by Hubert Wojciechowski and affect the news.php and image.php components of the CMS.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"e107 CMS v3.2.1 - Reflected XSS via Comment Flow","id":"CVE-2022-50905","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"e107:e107","products":["e107:e107"],"type":"xss","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"e107 CMS v3.2.1 - Admin Upload Restriction Bypass + Stored XSS","id":"CVE-2022-50906"},"packages":[],"prev":{"headline":"Wondershare UBackit 2.0.5 - 'wsbackup' Unquoted Service Path","id":"CVE-2022-50904"},"products":["e107 CMS"],"published":"2026-01-13","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2021-27885","kev_date_added":null,"published":"2021-03-02"},{"cvss_score":8.8,"headline":"Deserialization in n/a","id":"CVE-2016-10753","kev_date_added":null,"published":"2019-05-24"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-15901","kev_date_added":null,"published":"2018-08-28"},{"cvss_score":8.7,"headline":"e107 CMS v3.2.1 - Upload restriction bypass (Authenticated [Admin])+ Server file override","id":"CVE-2022-50916","kev_date_added":null,"published":"2026-01-13"},{"cvss_score":8.6,"headline":"e107 CMS v3.2.1 - Admin Upload Restriction Bypass + RCE","id":"CVE-2022-50907","kev_date_added":null,"published":"2026-01-13"},{"cvss_score":8.6,"headline":"e107 CMS v3.2.1 - Upload Restriction Bypass with Path Traversal File Override","id":"CVE-2022-50939","kev_date_added":null,"published":"2026-01-13"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2011-1513","kev_date_added":null,"published":"2011-11-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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-07","vendors":["e107"]},"summary":"Attackers can inject malicious scripts via reflected XSS in comments or stored XSS via SVG uploads, potentially compromising user sessions.","url":"https://insights.sbomify.com/CVE-2022-50905/"}