{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-25105 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-25105 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-25105 is a medium-severity cross-site scripting vulnerability in Unknown Ivory Search – WordPress Search Plugin, published on 7 Feb 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-25105 and fix it if it is affected.\n\nWhat it is: CVE-2021-25105 is a medium-severity cross-site scripting vulnerability in Unknown Ivory Search – WordPress Search Plugin, published on 7 Feb 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-25105 in the wild and no public exploit code.\n\nAffected product: Unknown Ivory Search – WordPress Search Plugin. 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-2021-25105/ (Markdown: https://insights.sbomify.com/CVE-2021-25105/index.md)","id":"CVE-2021-25105","markdown":"https://insights.sbomify.com/CVE-2021-25105/index.md","name":"CVE-2021-25105","record":{"aliases":["GHSA-mr9w-hm8q-hjg9"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"High-privilege users can inject malicious scripts via unescaped form settings in the Ivory Search WordPress plugin, potentially leading to code execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"ivory_search","vendor":"ivorysearch"}],"cvss":{"score":4.8,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/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":"The Ivory Search WordPress plugin before 5.4.1 does not escape some of the Form settings, which could allow high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed.","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":"Ivory Search \u003c 5.4.1 - Multiple Admin+ Stored Cross-Site Scripting","id":"CVE-2021-25105","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"WPLegalPages \u003c 2.7.1 - Subscriber+ Arbitrary Settings Update to Stored XSS","id":"CVE-2021-25106"},"packages":[],"prev":{"headline":"Ocean Extra \u003c 1.9.5 - Reflected Cross-Site Scripting","id":"CVE-2021-25104"},"products":["Ivory Search – WordPress Search Plugin"],"published":"2022-02-07","related":[{"cvss_score":6.1,"headline":"Ivory Search \u003c 4.6.1 - Reflected Cross Site Scripting (XSS)","id":"CVE-2021-24234","kev_date_added":null,"published":"2021-04-22"},{"cvss_score":5.3,"headline":"Ivory Search – WordPress Search Plugin \u003c= 5.5.6 - Information Exposure via AJAX Search Form","id":"CVE-2024-6835","kev_date_added":null,"published":"2024-09-05"},{"cvss_score":4.8,"headline":"Ivory Search \u003c 5.5.10 - Admin+ Stored XSS","id":"CVE-2025-5209","kev_date_added":null,"published":"2025-06-17"},{"cvss_score":4.8,"headline":"WordPress Ivory Search plugin \u003c= 4.6.6 - Reflected Cross-Site Scripting (XSS) vulnerability","id":"CVE-2021-36869","kev_date_added":null,"published":"2021-10-21"}],"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":["Unknown"]},"summary":"High-privilege users can inject malicious scripts via unescaped form settings in the Ivory Search WordPress plugin, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2021-25105/"}