{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-39530 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-39530 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-39530 is a high-severity cross-site scripting vulnerability in dsky Site Search 360, published on 16 Apr 2025. 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-2025-39530 and fix it if it is affected.\n\nWhat it is: CVE-2025-39530 is a high-severity cross-site scripting vulnerability in dsky Site Search 360, published on 16 Apr 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-39530 in the wild and no public exploit code.\n\nAffected product: dsky Site Search 360. 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-2025-39530/ (Markdown: https://insights.sbomify.com/CVE-2025-39530/index.md)","id":"CVE-2025-39530","markdown":"https://insights.sbomify.com/CVE-2025-39530/index.md","name":"CVE-2025-39530","record":{"aliases":["GHSA-xvgw-45wp-xpq2"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can inject malicious scripts via CSRF, leading to stored XSS and potential account takeover in Site Search 360.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross-Site Request Forgery (CSRF) vulnerability in dsky Site Search 360 site-search-360 allows Stored XSS.This issue affects Site Search 360: from n/a through \u003c= 2.1.8.","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":"WordPress Site Search 360 plugin \u003c= 2.1.8 - Cross Site Request Forgery (CSRF) to stored XSS vulnerability","id":"CVE-2025-39530","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Slazzer Background Changer plugin \u003c= 3.14 - Broken Access Control Vulnerability","id":"CVE-2025-39531"},"packages":[],"prev":{"headline":"WordPress Scriptless Social Sharing plugin \u003c= 3.3.0 - Cross Site Scripting (XSS) Vulnerability","id":"CVE-2025-39529"},"products":["Site Search 360"],"published":"2025-04-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["dsky"]},"summary":"Attackers can inject malicious scripts via CSRF, leading to stored XSS and potential account takeover in Site Search 360.","url":"https://insights.sbomify.com/CVE-2025-39530/"}