{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1625 exists.","fix":"No fix has been published for CVE-2025-1625 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-1625 is a medium-severity cross-site scripting vulnerability in Unknown Qi Blocks, published on 19 May 2025. 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-2025-1625 and fix it if it is affected.\n\nWhat it is: CVE-2025-1625 is a medium-severity cross-site scripting vulnerability in Unknown Qi Blocks, published on 19 May 2025. Any signed-in user can exploit it over the network, 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-2025-1625 exists.\n\nAffected product: Unknown Qi Blocks. 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-1625/ (Markdown: https://insights.sbomify.com/CVE-2025-1625/index.md)","id":"CVE-2025-1625","markdown":"https://insights.sbomify.com/CVE-2025-1625/index.md","name":"CVE-2025-1625","record":{"aliases":["GHSA-mhq7-845r-m6gh"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Contributors can inject malicious scripts via Counter block options in Qi Blocks, leading to stored XSS attacks on WordPress sites.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"qi_blocks","vendor":"qodeinteractive"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","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":"The Qi Blocks WordPress plugin before 1.4 does not validate and escape some of its Counter block options before outputting them back in a page/post where the block is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Qi Blocks \u003c 1.4 - Contributor+ Stored XSS via Counter Block","id":"CVE-2025-1625","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Qi Blocks \u003c 1.4 - Contributor+ Stored XSS vi Countdown Block","id":"CVE-2025-1626"},"packages":[],"prev":{"headline":"GDPR Cookie Compliance \u003c 4.15.9 - Admin+ Stored XSS","id":"CVE-2025-1624"},"products":["Qi Blocks"],"published":"2025-05-19","related":[{"cvss_score":7.5,"headline":"WordPress Qi Blocks plugin \u003c= 1.3.2 - Local File Inclusion vulnerability","id":"CVE-2024-49690","kev_date_added":null,"published":"2024-10-23"},{"cvss_score":6.5,"headline":"WordPress Qi Blocks plugin \u003c= 1.3 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-38712","kev_date_added":null,"published":"2024-07-20"},{"cvss_score":6.4,"headline":"Qi Blocks \u003c= 1.2.9 - Authenticated (Author+) Stored Cross-Site Scripting","id":"CVE-2024-5221","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":5.4,"headline":"Qi Blocks \u003c 1.4 - Contributor+ Stored XSS vi Countdown Block","id":"CVE-2025-1626","kev_date_added":null,"published":"2025-05-19"},{"cvss_score":5.4,"headline":"Qi Blocks \u003c 1.4 - Contributor+ Stored XSS via ToC Block","id":"CVE-2025-1627","kev_date_added":null,"published":"2025-05-19"}],"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":"partial"},"state":"PUBLISHED","updated":"2026-01-09","vendors":["Unknown"]},"summary":"Contributors can inject malicious scripts via Counter block options in Qi Blocks, leading to stored XSS attacks on WordPress sites.","url":"https://insights.sbomify.com/CVE-2025-1625/"}