CVE-2020-26511 json
The wpo365-login plugin before v11.7 for WordPress allows use of a symmetric algorithm to decrypt a JWT token.
published 6y ago modified 4mo ago also EUVD-2020-19058
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- wpo365 wordpress_+_azure_ad_/_microsoft_office_365 11.7
Is CVE-2020-26511 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.15% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-287 Improper Authentication
- Technology feeds
References
-
plugins.trac.wordpress.org
/changeset/2388992/
patch, third-party-advisory
-
wpo365.com
/change-log/
release-notes, vendor-advisory
-
wordpress.org
/plugins/wpo365-login/#developers
product, third-party-advisory
-
wpvulndb.com
/vulnerabilities/10418
third-party-advisory
Sources
- CVE List CVE-2020-26511
- NVD CVE-2020-26511
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.