{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-22386 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-22386 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-22386 is a high-severity vulnerability in n/a, published on 4 Jan 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-22386 and fix it if it is affected.\n\nWhat it is: CVE-2025-22386 is a high-severity vulnerability in n/a, published on 4 Jan 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-22386 in the wild and no public exploit code.\n\nAffected product: n/a. 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-22386/ (Markdown: https://insights.sbomify.com/CVE-2025-22386/index.md)","id":"CVE-2025-22386","markdown":"https://insights.sbomify.com/CVE-2025-22386/index.md","name":"CVE-2025-22386","record":{"aliases":["GHSA-jcgv-xjw5-6wp4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Optimizely Configured Commerce","requires_auth":"low_privilege","summary":"Attackers can reuse session tokens from logged-out users to maintain unauthorized access to the B2B storefront.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"configured_commerce","vendor":"optimizely"}],"cvss":{"score":7.3,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"An issue was discovered in Optimizely Configured Commerce before 5.2.2408. A medium-severity session issue exists in the Commerce B2B application, affecting the longevity of active sessions in the storefront. This allows session tokens tied to logged-out sessions to still be active and usable.","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":"Security feature bypass in n/a","id":"CVE-2025-22386","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2025-22387"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2025-22385"},"products":["n/a"],"published":"2025-01-04","related":[{"cvss_score":8.1,"headline":"Cross-site scripting in n/a","id":"CVE-2024-56174","kev_date_added":null,"published":"2024-12-18"},{"cvss_score":7.5,"headline":"Business logic in n/a","id":"CVE-2025-22384","kev_date_added":null,"published":"2025-01-04"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2025-22387","kev_date_added":null,"published":"2025-01-04"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2024-56175","kev_date_added":null,"published":"2024-12-18"},{"cvss_score":5.9,"headline":"Missing authorization in n/a","id":"CVE-2025-22385","kev_date_added":null,"published":"2025-01-04"},{"cvss_score":4.7,"headline":"Cross-site scripting in n/a","id":"CVE-2024-56173","kev_date_added":null,"published":"2024-12-18"}],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-06","vendors":["n/a"]},"summary":"Attackers can reuse session tokens from logged-out users to maintain unauthorized access to the B2B storefront.","url":"https://insights.sbomify.com/CVE-2025-22386/"}