Keyring
Keyring has one disclosed vulnerability in the WordSec catalog, all reported in 2014; it is fixed as of September 2026. Their average CVSS score is 6.1, and the most serious one scores 6.1 out of 10.
The most common weakness is Cross-Site Scripting, behind 1 of the records (100%).
The one issue recorded for Keyring has a vendor fix available, so running the current release closes it.
All of these findings were reported by Anant Shrivastava (anantshri). Keyring is installed on roughly 1,000 WordPress sites, so each unpatched flaw has a wide blast radius. The current release is tested up to WordPress 6.2.11.
Keyring < 1.5.1 - Cross-Site Scripting
Read the full analysisVulnerability Records
Keyring
Author
Beau Lebens
See the Keyring Developer’s Guide for more details. Keyring provides a very hookable, completely customizable framework for connecting your WordPress to an external service. It takes care of all the heavy lifting when making authenticated requests, so all you need to do is implement cool features and not worry about these tricky bits. Out of the box, Keyring currently comes with base Service definitions for: HTTP Basic, OAuth1, and OAuth2. And includes ready-to-use definitions for: 500px Delicious Eventbrite Facebook Fitbit Flickr Foursquare Google Analytics Google Contacts Google Mail Instagram Instapaper Jetpack/WordPress.com LinkedIn Moves Nest Pinterest RunKeeper Strava TripIt Tumblr Twitter Yahoo! Updates YouTube You can very easily write your own Service definitions and then use all the power of Keyring to hook into that authentication flow. See the Keyring Developer’s Guide for more details. Contributions are welcome via Github pull request.
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C