Json Api Auth
Monthly
Authentication bypass in the WordPress plugin JSON API Auth (all versions up to and including 3.1.2) lets unauthenticated remote attackers harvest a live Administrator logged_in cookie from a cached JSON response and use it to take over the site. The underlying defect sits in the required PI-Media/json-api parent plugin, whose controller-dispatch transient cache is keyed only by URI and query string with HTTP method and POST body ignored, so the authenticated /api/auth/generate_auth_cookie/ response - which embeds a wp_generate_auth_cookie() session cookie directly in its JSON body - is replayed to any subsequent unauthenticated GET, with the plugin's nominal HTTPS enforcement trivially defeated by passing insecure=cool. Our independent assessment keeps the full confidentiality and integrity impact of the vendor vector but treats the access complexity as High (base 8.1 rather than 9.8) because exploitation is opportunistic and conditional: both plugins must be installed and active with the Auth controller enabled, and a legitimate Administrator must have POSTed to the cookie-generation endpoint within the preceding 24-hour transient TTL; no public exploit identified at time of analysis.
Authentication bypass in the WordPress plugin JSON API Auth (all versions up to and including 3.1.2) lets unauthenticated remote attackers harvest a live Administrator logged_in cookie from a cached JSON response and use it to take over the site. The underlying defect sits in the required PI-Media/json-api parent plugin, whose controller-dispatch transient cache is keyed only by URI and query string with HTTP method and POST body ignored, so the authenticated /api/auth/generate_auth_cookie/ response - which embeds a wp_generate_auth_cookie() session cookie directly in its JSON body - is replayed to any subsequent unauthenticated GET, with the plugin's nominal HTTPS enforcement trivially defeated by passing insecure=cool. Our independent assessment keeps the full confidentiality and integrity impact of the vendor vector but treats the access complexity as High (base 8.1 rather than 9.8) because exploitation is opportunistic and conditional: both plugins must be installed and active with the Auth controller enabled, and a legitimate Administrator must have POSTed to the cookie-generation endpoint within the preceding 24-hour transient TTL; no public exploit identified at time of analysis.