Mstore Api Create Native Android Ios Apps On The Cloud
Monthly
Authentication bypass in the InspireUI Mstore API plugin for WordPress (versions up to and including 4.20.0) lets unauthenticated attackers forge Firebase Phone Auth JWTs and impersonate any phone number. The FirebasePhoneAuthHelper::verify_id_token() function checks token claims (alg, kid, aud, iss) but never verifies the cryptographic signature against Google's public certificates, so an attacker can sign a token with their own RSA key and log into or create arbitrary WordPress accounts. Reported by Wordfence with a CVSS of 9.8; no public exploit identified at time of analysis and the plugin is not in CISA KEV.
Authenticated subscribers and above in WordPress sites using MStore API plugin up to version 4.18.3 can modify arbitrary user meta fields on their own accounts, including legacy privilege escalation keys like wp_user_level and plugin-specific authorization flags, potentially leading to privilege escalation or stored XSS. The vulnerability stems from the update_user_profile() function accepting unsanitized, user-supplied meta_data JSON without allowlist or validation before passing it directly to update_user_meta(). No public exploit code or active exploitation has been identified at this time.
Authentication bypass in the InspireUI Mstore API plugin for WordPress (versions up to and including 4.20.0) lets unauthenticated attackers forge Firebase Phone Auth JWTs and impersonate any phone number. The FirebasePhoneAuthHelper::verify_id_token() function checks token claims (alg, kid, aud, iss) but never verifies the cryptographic signature against Google's public certificates, so an attacker can sign a token with their own RSA key and log into or create arbitrary WordPress accounts. Reported by Wordfence with a CVSS of 9.8; no public exploit identified at time of analysis and the plugin is not in CISA KEV.
Authenticated subscribers and above in WordPress sites using MStore API plugin up to version 4.18.3 can modify arbitrary user meta fields on their own accounts, including legacy privilege escalation keys like wp_user_level and plugin-specific authorization flags, potentially leading to privilege escalation or stored XSS. The vulnerability stems from the update_user_profile() function accepting unsanitized, user-supplied meta_data JSON without allowlist or validation before passing it directly to update_user_meta(). No public exploit code or active exploitation has been identified at this time.