CVE-2023-3752
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 · uneditedA vulnerability was found in Creativeitem Academy LMS 5.15. It has been rated as problematic. Affected by this issue is some unknown functionality of the file /home/courses. The manipulation of the argument sort_by leads to cross site scripting. The attack may be launched remotely. VDB-234422 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceA reflected cross-site scripting (XSS) vulnerability exists in the Creativeitem Academy LMS version 5.15. The 'sort_by' parameter on the /home/courses page does not properly sanitize user input before rendering it in the HTML output, allowing an attacker to inject malicious JavaScript code that executes in the victim's browser.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 5.15CVSS 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
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 Creativeitem Academy LMS is installedLocate the LMS installation directory and check for version identifiers in the codebase, typically in a version file, composer.json, or application metadataAffected if The application is Creativeitem Academy LMS version 5.15
-
Identify the courses page handlerLocate the route/controller handling /home/courses - typically in the routing configuration or controller directory - and find the code that processes the 'sort_by' parameterAffected if The 'sort_by' parameter is processed without sanitization in the courses controller
-
Examine input handling for sort_by parameterReview the code where $_GET['sort_by'] or equivalent framework request input is used, and check if it is passed directly to the view/template without escaping functions like htmlspecialchars()Affected if The sort_by value is rendered in HTML without output encoding/escaping
-
Test reflected XSS via HTTP requestSend a GET request to /home/courses?sort_by=<script>alert(1)</script> and inspect the response HTML to see if the script tag appears unescapedAffected if The malicious script tag is reflected unescaped in the page source
The environment is affected if Creativeitem Academy LMS version 5.15 is installed and the /home/courses page reflects the sort_by parameter without HTML escaping.
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 proper input validation and output encoding for the sort_by parameter. Use context-appropriate escaping when rendering the sort_by value in HTML, and consider implementing a Content Security Policy (CSP) as defense-in-depth.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3752 — 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-2023-3752 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