PŽ
    /
    Zpět na blog
    Security Sunday

    One Web App, One Breach: What Happened at Charles University


    One Web App, One Breach: What Happened at Charles University

    image

    An attacker used a single compromised web application to pull personal data from the central student system of the Czech Republic’s largest university. What’s confirmed, what isn’t, and what any organization with web apps tied to important data should take from it.

    Hi, I’m Patrik Žák, and welcome to Security Sunday.

    On Friday, November 13, Charles University in Prague asked all of its students, about 55,000 people, to change their passwords within ten days. The reason: an attacker used one compromised web application to reach data in the university’s central Study Information System and downloaded part of it, including personal data.

    This isn’t a small faculty or a forgotten website. The study system is the central record of studies at the largest university in the Czech Republic.

    Here’s what the university has confirmed and what it hasn’t, why one application was enough, and what any organization with an internet-facing app connected to important data should take from it.

    What happened

    On Friday, November 13, Charles University announced it was dealing with a cyber incident. According to its statement, an attacker compromised one of its web applications and used it to gain unauthorized access to data in the central Study Information System, known as SIS. The attacker obtained and downloaded part of that data, including personal data.

    The university took the compromised application offline, secured access, reported the incident to NÚKIB, the Czech national cybersecurity agency, and filed a criminal complaint against an unknown perpetrator. Prague police spokesperson Richard Hrdina confirmed the police had received the complaint and are looking into it. NÚKIB’s spokesperson said the agency is handling the incident but gave no details.

    All users of the university’s CAS login service must change their password within ten days of the request. The university calls it a precaution and says it doesn’t mean that passwords were cracked or that all users’ accounts were accessed.

    Confirmed vs. unknown

    What’s confirmed: the attacker downloaded data from the study system, and it includes personal data. The university added that its investigation so far has not confirmed any broad compromise of user accounts or disruption of its central information systems.

    What we don’t know yet: how many people are affected, exactly what data left, which application it was, and whether the data has surfaced anywhere. The university says it’s still working that out. Nobody has named a culprit.

    One more thing that got mixed up in early reports. On Tuesday, November 10, the university had already published an incident in the networks of its Third Faculty of Medicine and Faculty of Arts, and asked for password changes there too. It hasn’t said whether that’s connected to the access to the study system. On the day of the announcement, part of the university’s email was also down because of a Microsoft outage, which the university says didn’t originate on its side.

    Why one application was enough

    Large organizations don’t have one system; they have dozens of applications around it. Timetables, applications, enrollment, records, reporting. Each needs some access to the core system, and each is another door.

    At Charles University, all we know is that one application with access to study system data was compromised. How, the university hasn’t said. But in my experience from penetration tests, this is generally one of the most common scenarios: the core system is well guarded, but the app on the edge, built years ago by another vendor or team, much less so.

    Universities have it harder than companies. They have tens of thousands of users who change every year, faculties with their own IT, and plenty of applications built over the past twenty years. And according to NÚKIB’s quarterly report, intrusions in the Czech Republic mainly hit public administration, education and healthcare.

    What students face now

    The most immediate risk isn’t the leak itself, but what comes after it. We don’t yet know exactly what data left. Take a hypothetical example the university hasn’t confirmed: anyone with a name, an email address and the faculty someone studies at can write a very convincing phishing email, something like “due to the incident, verify your account here.”

    The university warns about this itself: official emails come from the cuni.cz domain and shouldn’t contain links, or at most links to cuni.cz pages. Suspicious messages can be forwarded to the university security team at abuse@cuni.cz. If you study or teach there, change your password directly on the university website, not through a link in an email, and don’t reuse that password anywhere else.

    What to take from this

    First, list every web application that has access to your key data, including those run by a vendor or another department. Each one is a possible way in.

    Second, give each application only the data it actually needs. A timetable app doesn’t need to see every user’s personal data.

    Third, watch for unusual data reads. When an application suddenly pulls far more records than usual, something should flag it.

    And fourth, have user communication ready, including a phishing warning. Charles University handled that quickly and clearly.

    The short version

    An attacker used one web application to reach data in Charles University’s study system and downloaded part of it, including personal data. The university took the app offline, reported the incident and asked users to change passwords. The scope and the attacker are still unknown.

    The takeaway? Attackers don’t come through your strongest door. They come through the application you forgot about.

    If you want to know how resilient your web applications that touch important data really are, get in touch at team@sysnetshield.com. That’s exactly what we test in a web application penetration test.

    See you next Sunday.

    © 2026 Patrik Žák. Všechna práva vyhrazena.