{"answers":{"affected":"2 open source packages ship an affected version, including radiant. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-7261 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-7261 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-7261 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 Feb 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-7261 and fix it if it is affected.\n\nWhat it is: CVE-2018-7261 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 Feb 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-7261 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- radiant (RubyGems): affected all versions; no fix listed\n- radiant (RubyGems): affected all versions; no fix listed\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-2018-7261/ (Markdown: https://insights.sbomify.com/CVE-2018-7261/index.md)","id":"CVE-2018-7261","markdown":"https://insights.sbomify.com/CVE-2018-7261/index.md","name":"CVE-2018-7261","record":{"aliases":["GHSA-gp82-xr77-88f4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Radiant CMS","requires_auth":"low_privilege","summary":"Persistent XSS in Radiant CMS allows attackers to inject scripts via user preferences and configuration fields, potentially leading to session hijacking or code execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"radiant_cms","vendor":"radiantcms"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"There are multiple Persistent XSS vulnerabilities in Radiant CMS 1.1.4. They affect Personal Preferences (Name and Username) and Configuration (Site Title, Dev Site Domain, Page Parts, and Page Fields).","ecosystems":["RubyGems"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"radiant vulnerable to Cross-site Scripting","id":"CVE-2018-7261","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"xss","year":"2018"},"n_packages":2,"n_references":2,"next":{"headline":"Null dereference in n/a","id":"CVE-2018-7262"},"packages":[{"ecosystem":"RubyGems","fixed":[],"introduced":[],"last_affected":[],"package":"radiant","purl":null,"source":"GHSA-gp82-xr77-88f4"},{"ecosystem":"RubyGems","fixed":[],"introduced":[],"last_affected":[],"package":"radiant","purl":"pkg:gem/radiant","source":"GHSA-gp82-xr77-88f4"}],"prev":{"headline":"phpMyAdmin Cross-site scripting (XSS) vulnerability in central columns feature","id":"CVE-2018-7260"},"products":["n/a"],"published":"2018-02-21","related":[{"cvss_score":5.4,"headline":"Radiant CMS vulnerable to Cross-site Scripting","id":"CVE-2018-5216","kev_date_added":null,"published":"2018-01-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Persistent XSS in Radiant CMS allows attackers to inject scripts via user preferences and configuration fields, potentially leading to session hijacking or code execution.","url":"https://insights.sbomify.com/CVE-2018-7261/"}