{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-7617 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-7617 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-7617 is a medium-severity missing authorization vulnerability in Secufor_OAuth, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-7617 and fix it if it is affected.\n\nWhat it is: CVE-2026-7617 is a medium-severity missing authorization vulnerability in Secufor_OAuth, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-7617 in the wild and no public exploit code.\n\nAffected product: Secufor_OAuth. 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-2026-7617/ (Markdown: https://insights.sbomify.com/CVE-2026-7617/index.md)","id":"CVE-2026-7617","markdown":"https://insights.sbomify.com/CVE-2026-7617/index.md","name":"CVE-2026-7617","record":{"aliases":["GHSA-rcgx-vphg-9xcg"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can disconnect the WordPress site from its Secufor account by clearing stored login tokens due to missing authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The Secufor_OAuth plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 1.0.7. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to disconnect the WordPress site from its linked Secufor account by clearing the plugin's stored login token and user login configuration.","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":"Missing authorization in Secufor OAuth","id":"CVE-2026-7617","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"SQL injection in EnvíaloSimple: Email Marketing y Newsletters","id":"CVE-2026-7618"},"packages":[],"prev":{"headline":"Zawgyi Embed \u003c= 2.1.1 - Cross-Site Request Forgery via 'zawgyi_forceCSS' Parameter","id":"CVE-2026-7616"},"products":["Secufor_OAuth"],"published":"2026-06-24","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":"partial"},"state":"PUBLISHED","updated":"2026-06-24","vendors":["secufor"]},"summary":"Unauthenticated attackers can disconnect the WordPress site from its Secufor account by clearing stored login tokens due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2026-7617/"}