{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-25413 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-25413 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-25413 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Feb 2022. 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-2022-25413 and fix it if it is affected.\n\nWhat it is: CVE-2022-25413 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Feb 2022. 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-2022-25413 in the wild and no public exploit code.\n\nAffected product: n/a. 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-25413/ (Markdown: https://insights.sbomify.com/CVE-2022-25413/index.md)","id":"CVE-2022-25413","markdown":"https://insights.sbomify.com/CVE-2022-25413/index.md","name":"CVE-2022-25413","record":{"aliases":["GHSA-6wm7-76mj-3m8h"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Maxsite CMS","requires_auth":"low_privilege","summary":"Stored XSS in Maxsite CMS allows attackers to inject malicious scripts via the f_tags parameter, 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":"maxsite_cms","vendor":"max-3000"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/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":"Maxsite CMS v108 was discovered to contain a stored cross-site scripting (XSS) vulnerability via the parameter f_tags at /admin/page_edit/3.","ecosystems":[],"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":"Cross-site scripting in n/a","id":"CVE-2022-25413","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2022-25414"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2022-25412"},"products":["n/a"],"published":"2022-02-28","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2022-25411","kev_date_added":null,"published":"2022-02-28"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2021-27983","kev_date_added":null,"published":"2021-12-10"},{"cvss_score":8.1,"headline":"Path traversal in n/a","id":"CVE-2022-25412","kev_date_added":null,"published":"2022-02-28"},{"cvss_score":6.9,"headline":"MaxSite CMS MarkItUp Preview AJAX Endpoint preview-ajax.php eval code injection","id":"CVE-2026-3395","kev_date_added":null,"published":"2026-03-01"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2022-25410","kev_date_added":null,"published":"2022-02-28"},{"cvss_score":5.3,"headline":"MaxSite CMS HTTP Header uploads-require-maxsite.php unrestricted upload","id":"CVE-2025-12346","kev_date_added":null,"published":"2025-10-28"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Stored XSS in Maxsite CMS allows attackers to inject malicious scripts via the f_tags parameter, potentially leading to session hijacking or code execution.","url":"https://insights.sbomify.com/CVE-2022-25413/"}