{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26511 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-26511 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-26511 is a high-severity authentication bypass vulnerability in n/a, published on 2 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-26511 and fix it if it is affected.\n\nWhat it is: CVE-2020-26511 is a high-severity authentication bypass vulnerability in n/a, published on 2 Oct 2020. 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-2020-26511 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-2020-26511/ (Markdown: https://insights.sbomify.com/CVE-2020-26511/index.md)","id":"CVE-2020-26511","markdown":"https://insights.sbomify.com/CVE-2020-26511/index.md","name":"CVE-2020-26511","record":{"aliases":["GHSA-28p2-p7pc-m535"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress login plugin","requires_auth":"none","summary":"An attacker can bypass authentication in the wpo365-login WordPress plugin by exploiting weak JWT decryption, allowing unauthorized access.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wordpress_\\+_azure_ad_\\/_microsoft_office_365","vendor":"wpo365"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"The wpo365-login plugin before v11.7 for WordPress allows use of a symmetric algorithm to decrypt a JWT token. This leads to authentication bypass.","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":"Auth bypass in n/a","id":"CVE-2020-26511","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":0,"n_references":4,"next":{"headline":"XML external entity in n/a","id":"CVE-2020-26513"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2020-26510"},"products":["n/a"],"published":"2020-10-02","related":[{"cvss_score":9.3,"headline":"WPO365 | LOGIN - Wordpress Plugin Persistent Cross-Site Scripting","id":"CVE-2021-43409","kev_date_added":null,"published":"2021-11-19"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"An attacker can bypass authentication in the wpo365-login WordPress plugin by exploiting weak JWT decryption, allowing unauthorized access.","url":"https://insights.sbomify.com/CVE-2020-26511/"}