CVE-2026-47324
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedProjectsAndPrograms school-management-system is vulnerable to Stored Cross‑Site Scripting (XSS) in multiple attributes of students and teachers objects. An authorized attacker (e.g., a teacher or administrator) can inject malicious JavaScript that is subsequently executed in other users’ browsers. Critically, when chained with CVE‑2025‑11661, which allows unauthenticated access to backend endpoints, this vulnerability can be exploited by a remote attacker without privileges to inject and execute arbitrary JavaScript. The maintainers were notified early about this vulnerability but did not provide details regarding affected versions. The version corresponding to commit 6b6fae5 was tested and confirmed vulnerable; other versions were not tested and may also be affected.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStored Cross-Site Scripting (XSS) vulnerability in the ProjectsAndPrograms school-management-system allows authorized users (teachers/administrators) to inject malicious JavaScript into student and teacher object attributes. When chained with CVE-2025-11661, unauthenticated remote attackers can exploit this flaw. The malicious payload persists in the database and executes in victim browsers when other users view the affected records.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- Authentication
- X
- User interaction
- P
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the application and its installed versionLocate the school-management-system application directory or check the software inventory/manifest file that lists the installed version number. Compare your version against any known version releases.Affected if The application is installed and your version has not received security updates for stored XSS vulnerabilities.
-
Verify student/teacher record input functionality existsAccess the application interfaces that allow creating or editing student and teacher profile records. These are typically found in admin or staff control panels under sections labeled 'Students', 'Teachers', 'Staff', or 'Users'.Affected if The application contains editable student or teacher record forms where user-supplied data can be saved to the database.
-
Test for reflected output of stored dataCreate or edit a test student/teacher record using the application interface. Enter a harmless test string containing HTML characters (such as <script>alert(1)</script> or <img src=x onerror=alert(1)>). Save the record, then view the same record as a different user or in a different view context.Affected if The entered characters render as unescaped HTML or JavaScript when you view the saved record, indicating missing output encoding.
-
Inspect database for unsanitized stored contentQuery the database tables that store student and teacher records (commonly named students, teachers, staff, users, or profiles). Look for records containing raw HTML tags, script elements, or event handler attributes in name, description, or other text fields.Affected if The database contains records with unescaped HTML or script tags in student or teacher fields, indicating the application stores input without sanitization.
-
Check for missing output encoding in application sourceExamine the application code that renders student and teacher data in views or templates. Look for places where database values are inserted into HTML without using encoding functions (such as htmlspecialchars, escape, or equivalent sanitization methods).Affected if The application renders student/teacher field values directly into HTML without applying context-aware encoding.
You are affected if the school-management-system is installed and its student/teacher record views display stored content without output encoding, allowing embedded JavaScript to execute when records are viewed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement robust input validation and output encoding for all student and teacher attributes, with particular focus on fields that accept user-supplied content. Sanitize existing database records to remove any stored payloads. Consider implementing Content Security Policy headers.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47324 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-47324 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data