Unauthenticated account access via forged Firebase JWTs
Published Sep 5, 2026 · Updated Sep 7, 2026
Authentication bypass in FluxBuilder MStore API 4.20.0 and earlier allows remote attackers to access WordPress accounts via forged JWTs. FirebasePhoneAuthHelper::verify_id_token() checks token claims but never verifies the JWT signature against Google's public key certificates. No credentials or user interaction are required; a self-signed token can impersonate any phone number to enter an existing account or create an arbitrary account.
Summary
What happened
Authentication bypass in FluxBuilder MStore API 4.20.0 and earlier allows remote attackers to access WordPress accounts via forged JWTs. FirebasePhoneAuthHelper::verify_id_token() checks token claims but never verifies the JWT signature against Google's public key certificates. No credentials or user interaction are required; a self-signed token can impersonate any phone number to enter an existing account or create an arbitrary account.
The record
- CVE
- CVE-2026-13447
- Published
- Sep 5, 2026
- Updated
- Sep 7, 2026
- Vendor
- FluxBuilder
- Product
- MStore API
- Classifications
- CWE-287, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 5, 2026CVE publishedPublication date reported by the CVE source.
- Sep 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=4.20.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo