{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-23475 exists.","fix":"No fix has been published for CVE-2022-23475 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-23475 is a high-severity cross-site scripting vulnerability in lirantal daloradius, published on 6 Dec 2022. 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-23475 and fix it if it is affected.\n\nWhat it is: CVE-2022-23475 is a high-severity cross-site scripting vulnerability in lirantal daloradius, published on 6 Dec 2022. 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-23475 exists.\n\nAffected product: lirantal daloradius. 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-23475/ (Markdown: https://insights.sbomify.com/CVE-2022-23475/index.md)","id":"CVE-2022-23475","markdown":"https://insights.sbomify.com/CVE-2022-23475/index.md","name":"CVE-2022-23475","record":{"aliases":["GHSA-c9xx-6mvw-9v84"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"RADIUS management application","requires_auth":"none","summary":"Attackers can hijack user accounts via XSS and CSRF vulnerabilities in the daloRADIUS web management interface.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"daloradius","vendor":"daloradius"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"daloRADIUS is an open source RADIUS web management application. daloRadius 1.3 and prior are vulnerable to a combination cross site scripting (XSS) and cross site request forgery (CSRF) vulnerability which leads to account takeover in the mng-del.php file because of an unescaped variable reflected in the DOM on line 116. This issue has been addressed in commit `ec3b4a419e`. Users are advised to manually apply the commit in order to mitigate this issue. Users may also mitigate this issue with in two parts 1) The CSRF vulnerability can be mitigated  by making the daloRadius session cookie to samesite=Lax or by the implimentation of a CSRF token in all forms. 2) The XSS vulnerability may be mitigated by escaping it or by introducing a Content-Security policy.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"dalorRadius full account take over","id":"CVE-2022-23475","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Unchecked return value from xmlTextReaderExpand in Nokogiri","id":"CVE-2022-23476"},"packages":[],"prev":{"headline":"editor.js contains Code Injection","id":"CVE-2022-23474"},"products":["daloradius"],"published":"2022-12-06","related":[{"cvss_score":7.2,"headline":"Improper Restriction of Names for Files and Other Resources in lirantal/daloradius","id":"CVE-2023-0046","kev_date_added":null,"published":"2023-01-04"},{"cvss_score":7.2,"headline":"Code Injection in lirantal/daloradius","id":"CVE-2023-0048","kev_date_added":null,"published":"2023-01-04"},{"cvss_score":5.8,"headline":"Cross-site Scripting (XSS) - Reflected in lirantal/daloradius","id":"CVE-2023-0337","kev_date_added":null,"published":"2023-01-17"},{"cvss_score":5.8,"headline":"Cross-site Scripting (XSS) - Reflected in lirantal/daloradius","id":"CVE-2023-0338","kev_date_added":null,"published":"2023-01-17"},{"cvss_score":5.3,"headline":"Sensitive Cookie Without 'HttpOnly' Flag in lirantal/daloradius","id":"CVE-2022-4630","kev_date_added":null,"published":"2022-12-21"},{"cvss_score":5.3,"headline":"Missing Authorization in lirantal/daloradius","id":"CVE-2022-4366","kev_date_added":null,"published":"2022-12-08"}],"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":"total"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["lirantal"]},"summary":"Attackers can hijack user accounts via XSS and CSRF vulnerabilities in the daloRADIUS web management interface.","url":"https://insights.sbomify.com/CVE-2022-23475/"}