CVE-2026-6956
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 · uneditedATutor is vulnerable to Reflected XSS in /install/install.php endpoint. An attacker can provide a specially crafted URL that, when opened, results in arbitrary JavaScript execution in the victim's browser. Product is no longer actively supported. Maintainers of this project were notified early about this vulnerability, but did not respond with the details of the vulnerability or vulnerable version range. Only version 2.2.4 was tested and confirmed as vulnerable, other versions were not tested but might also be vulnerable.
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 · moderate confidenceATutor versions prior to and including 2.2.4 contain a reflected cross-site scripting (XSS) vulnerability in the /install/install.php endpoint. The vulnerability allows remote attackers to inject arbitrary JavaScript into victim browsers via specially crafted URL parameters that are reflected back without proper sanitization or output encoding.
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
- None
- Authentication
- X
- User interaction
- A
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/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.
-
Confirm ATutor installationLocate the ATutor application by searching for ATutor-specific directories (e.g., /ATutor/, /atutor/) or files such as 'include/lib/init.inc.php', 'header.php', or 'footer.php' containing 'ATutor' branding in the web root.Affected if ATutor is not present on the system.
-
Identify installed ATutor versionCheck the version.php file typically located at /include/atutor_version.php or /include/version.php within the ATutor directory. Alternatively, view the source of any ATutor page and look for version information in the footer or about page.Affected if The discovered version is 2.2.4 or any version prior to 2.2.4.
-
Verify install.php existsCheck if the file /install/install.php exists in the ATutor web root directory. This can be done via file system inspection or by attempting to access the URL (e.g., https://target/install/install.php).Affected if The /install/install.php file exists and is accessible via HTTP/HTTPS.
-
Confirm install functionality is enabledAccess the /install/install.php endpoint and verify it loads the installation wizard rather than redirecting or displaying a disabled message. Check if the page accepts and reflects URL parameters back in the response.Affected if The install.php page loads and reflects URL parameter values without sanitization.
You are affected if ATutor version 2.2.4 or earlier is installed and the /install/install.php file is accessible and reflects URL parameters without proper encoding.
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 dataSince ATutor is no longer actively maintained, the recommended mitigation is to remove or disable the /install/install.php file if the application is already deployed, or implement proper input validation and output encoding in the affected endpoint if the install functionality is still required.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6956 — 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-6956 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