CVE-2020-26511
First published: Fri Oct 02 2020(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Wpo365 Wordpress + Azure Ad / Microsoft Office 365 | <11.7 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2020-26511?
CVE-2020-26511 is considered a high severity vulnerability due to the potential for authentication bypass.
How do I fix CVE-2020-26511?
To fix CVE-2020-26511, update the wpo365-login plugin to version 11.7 or later.
What type of vulnerability is CVE-2020-26511?
CVE-2020-26511 is an authentication bypass vulnerability.
Which versions of the wpo365-login plugin are affected by CVE-2020-26511?
Versions of the wpo365-login plugin prior to 11.7 are affected by CVE-2020-26511.
What can happen if CVE-2020-26511 is exploited?
If exploited, CVE-2020-26511 allows unauthorized access to users' accounts by bypassing authentication.
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/remedy
- agent/severity
- agent/last-modified-date
- agent/author
- agent/weakness
- agent/event
- agent/description
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/wpo365
- canonical/wpo365 wordpress + azure ad / microsoft office 365