Privilege escalation via unvalidated verification data
Published Mar 11, 2026 · Updated Mar 11, 2026
Email-verification bypass in ClassroomIO before 0.2.6 allows remote attackers to mark arbitrary accounts as verified. The /api/verify handler accepts unsigned Base64-encoded profile data, while /rest/v1/profile trusts a client-supplied is_email_verified value without server-side authorization. No prior privileges or mailbox access are required for token forgery, allowing unauthorized organization membership and privilege escalation against targeted accounts.
Summary
What happened
Email-verification bypass in ClassroomIO before 0.2.6 allows remote attackers to mark arbitrary accounts as verified. The /api/verify handler accepts unsigned Base64-encoded profile data, while /rest/v1/profile trusts a client-supplied is_email_verified value without server-side authorization. No prior privileges or mailbox access are required for token forgery, allowing unauthorized organization membership and privilege escalation against targeted accounts.
The record
- CVE
- CVE-2025-67298
- Published
- Mar 11, 2026
- Updated
- Mar 11, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-290, CWE-639, CWE-345, T1098
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2026CVE publishedPublication date reported by the CVE source.
- Mar 11, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Weakness, pattern, technique
Public exploit references
- Email verification bypass proof of conceptproof of concept · demonstrated
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