CBSE Admitted a Student Data Leak It Spent a Week Denying — Now Banks Are Babysitting Its Portal

Technology69 articles covering this story· 2026-05-31

CBSE Admitted a Student Data Leak It Spent a Week Denying — Now Banks Are Babysitting Its Portal

Central Board of Secondary EducationComputer securityVulnerability (computing)Indian Institutes of TechnologyPublic domainWhite hat (computer security)
CBSE Admitted a Student Data Leak It Spent a Week Denying — Now Banks Are Babysitting Its Portal
"Old Swinford Hospital - Hagley Road, Stourbridge - Foley House and Maybury House" by ell brown is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.

When a teenage security researcher flagged serious vulnerabilities in CBSE's Online Scoring and Marking portal — widely referred to as the OSM system — the board's first instinct was to wave him off. That instinct cost it a week of credibility it could not afford. By the time CBSE issued a formal acknowledgment admitting "gaps" in the evaluation portal, the personal data of an estimated 20 lakh Class 12 students had already been described by cyber activists as exposed. The board's belated admission did not make the claim go away; it confirmed the essential shape of it.

The sequence matters. CBSE's original denial was not a carefully hedged "we are investigating" — it was a flat rejection of the researcher's findings. Only after the vulnerability claims circulated widely, attracted political attention, and were independently assessed did the board reverse course. That reversal, when it came, was framed as routine maintenance. It was not routine. Reversals of that kind, after public pressure on a denial, are the signature of an institution that manages optics before it manages risk.

Union Education Minister Dharmendra Pradhan subsequently directed CBSE to undertake a complete overhaul of its payment gateway infrastructure — a directive that implies the problem was never just one isolated flaw. Payment gateways handling re-evaluation fees sit at a junction between student identity data, financial credentials, and board records. If the portal's underlying architecture was vulnerable at the scoring and marking layer, the question regulators should be asking is how deep that vulnerability ran, and for how long it existed before a teenager with time and curiosity found it.

To shore up the payment layer before the June 1 re-evaluation window opens, CBSE has brought in four public-sector banks to assist with gateway operations. The board has also deployed cybersecurity specialists and teams drawn from the Indian Institutes of Technology to audit and harden the system. These are serious institutions, and their involvement is not cosmetic. But their presence also illustrates the gap between where CBSE's digital infrastructure actually was and where a board managing the examination records of millions of students should have been years ago.

The teenager at the center of this — whose public reaction to CBSE's eventual acknowledgment was a Honey Singh meme, which is precisely the energy the moment deserved — did the work that CBSE's own security protocols apparently failed to do. Bug bounty culture in India is young, inconsistently rewarded, and frequently met with the kind of institutional hostility this case demonstrated in its first week. The fact that a minor identified a critical flaw in a national examination board's portal is not a story about one clever kid. It is a story about the baseline security posture of public digital infrastructure in India.

Congress leader Jairam Ramesh, framing the incident as evidence of ministerial distraction, specifically pointed to the data of 20 lakh students as being at risk. The political overlay is predictable — opposition parties attach themselves to every government embarrassment — but the underlying number is not partisan spin. Twenty lakh students is two million people, most of them minors, whose board examination records, personal identifiers, and potentially financial information passed through a system that had confirmable, unpatched vulnerabilities at a moment of peak traffic and sensitivity.

CBSE has stated its goal is a "transparent and glitch-free process" for the re-evaluation cycle beginning June 1. That language appeared in a post on X, the platform of record for institutional reassurance in the social media era. Transparency, in the actual meaning of the word, would include a public accounting of what data was accessible, for how long, to whom, and what remediation has specifically been applied — not a bank partnership announcement and an IIT team photo-opportunity. Whether that accounting ever materializes is, at this point, the only question worth tracking.

The re-evaluation portal opens on schedule. The students who need to use it have no practical alternative. They will log in, submit fees through the overhauled gateway, and trust that the institutions responsible for their academic records have done enough in the intervening weeks. That trust is not unreasonable. But it is trust extended to a board that spent a week telling those same students there was nothing to worry about — until it admitted there was.

Who is covering this (18+ outlets)

See what people are saying about this story on X.