{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68910 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-68910 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-68910 is a critical vulnerability in blazethemes Blogzee, published on 22 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-68910 and fix it if it is affected.\n\nWhat it is: CVE-2025-68910 is a critical vulnerability in blazethemes Blogzee, published on 22 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-68910 in the wild and no public exploit code.\n\nAffected product: blazethemes Blogzee. 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-68910/ (Markdown: https://insights.sbomify.com/CVE-2025-68910/index.md)","id":"CVE-2025-68910","markdown":"https://insights.sbomify.com/CVE-2025-68910/index.md","name":"CVE-2025-68910","record":{"aliases":["GHSA-rjv5-9xjq-63w7"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress theme","requires_auth":"low_privilege","summary":"Attackers can upload malicious files to the Blogzee WordPress theme, potentially leading to remote code execution on the server.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[],"cvss":{"score":9.9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"Unrestricted Upload of File with Dangerous Type vulnerability in blazethemes Blogzee blogzee allows Using Malicious Files.This issue affects Blogzee: from n/a through \u003c= 1.0.5.","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 Blogzee theme \u003c= 1.0.5 - Arbitrary File Upload vulnerability","id":"CVE-2025-68910","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Solace theme \u003c= 2.1.16 - Broken Access Control vulnerability","id":"CVE-2025-68911"},"packages":[],"prev":{"headline":"WordPress Blogistic theme \u003c= 1.0.5 - Arbitrary File Upload vulnerability","id":"CVE-2025-68909"},"products":["Blogzee"],"published":"2026-01-22","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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["blazethemes"]},"summary":"Attackers can upload malicious files to the Blogzee WordPress theme, potentially leading to remote code execution on the server.","url":"https://insights.sbomify.com/CVE-2025-68910/"}