{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-12740 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-12740 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-12740 is a high-severity vulnerability in CORNELIUS Plack::Middleware::OAuth, published on 4 Jul 2026. 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-2026-12740 and fix it if it is affected.\n\nWhat it is: CVE-2026-12740 is a high-severity vulnerability in CORNELIUS Plack::Middleware::OAuth, published on 4 Jul 2026. 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-2026-12740 in the wild and no public exploit code.\n\nAffected product: CORNELIUS Plack::Middleware::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-12740/ (Markdown: https://insights.sbomify.com/CVE-2026-12740/index.md)","id":"CVE-2026-12740","markdown":"https://insights.sbomify.com/CVE-2026-12740/index.md","name":"CVE-2026-12740","record":{"aliases":["GHSA-rfx5-x6rx-6w25"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl OAuth middleware","requires_auth":"none","summary":"Attackers can link their provider account to a victim's session via CSRF, potentially gaining unauthorized access to the victim's account.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Plack::Middleware::OAuth versions through 0.10 for Perl do not support the OAuth 2.0 state parameter.\n\nRequestTokenV2 builds the provider authorization redirect without issuing a state value, and AccessTokenV2 exchanges the callback code and registers the resulting token into the session (register_session) without verifying that the callback corresponds to an authorization request this session initiated.\n\nAny application that uses this middleware for OAuth 2.0 login is exposed to login cross-site request forgery: because the callback is not bound to the session that began the flow, an attacker who starts an authorization with their own provider account can deliver the resulting callback to a victim, causing the victim's session to complete the attacker's authorization and associating the attacker's provider identity and access token with that session. Where the application persists this as an account link, the attacker may retain access to the victim's account through their own provider credentials.","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":"Plack::Middleware::OAuth versions through 0.10 for Perl do not support the OAuth 2.0 state parameter","id":"CVE-2026-12740","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"WP Fast Total Search \u003c= 1.80.280 - Unauthenticated SQL Injection","id":"CVE-2026-12741"},"packages":[],"prev":{"headline":"WP Easy Pay \u003c= 4.5.0 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Post Deletion","id":"CVE-2026-12739"},"products":["Plack::Middleware::OAuth"],"published":"2026-07-04","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":"total"},"state":"PUBLISHED","updated":"2026-07-06","vendors":["CORNELIUS"]},"summary":"Attackers can link their provider account to a victim's session via CSRF, potentially gaining unauthorized access to the victim's account.","url":"https://insights.sbomify.com/CVE-2026-12740/"}