{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-9627 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-9627 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-9627 is a medium-severity vulnerability in izem Run Log, published on 11 Sep 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-9627 and fix it if it is affected.\n\nWhat it is: CVE-2025-9627 is a medium-severity vulnerability in izem Run Log, published on 11 Sep 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-9627 in the wild and no public exploit code.\n\nAffected product: izem Run Log. 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-9627/ (Markdown: https://insights.sbomify.com/CVE-2025-9627/index.md)","id":"CVE-2025-9627","markdown":"https://insights.sbomify.com/CVE-2025-9627/index.md","name":"CVE-2025-9627","record":{"aliases":["GHSA-r3mg-5v47-jvpw"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick administrators into modifying Run Log plugin settings via forged requests, requiring an upgrade to fix.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Run Log plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.7.10. This is due to missing or incorrect nonce validation on the oirl_plugin_options function. This makes it possible for unauthenticated attackers to modify plugin settings including distance units, pace display preferences, style themes, and display positions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.","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":"Run Log \u003c= 1.7.10 - Cross-Site Request Forgery to Settings Update","id":"CVE-2025-9627","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"The integration of the AMO.CRM \u003c= 1.0.1 - Cross-Site Request Forgery","id":"CVE-2025-9628"},"packages":[],"prev":{"headline":"Page Blocks \u003c= 1.1.0 - Cross-Site Request Forgery","id":"CVE-2025-9626"},"products":["Run Log"],"published":"2025-09-11","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-08","vendors":["izem"]},"summary":"Attackers can trick administrators into modifying Run Log plugin settings via forged requests, requiring an upgrade to fix.","url":"https://insights.sbomify.com/CVE-2025-9627/"}