dbcve.org
Mastery LmsApplication · Creativeitem

CVE-2023-3753

MEDIUM · 6.1 CVSS v3.1 Published 2023-07-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A vulnerability classified as problematic has been found in Creativeitem Mastery LMS 1.2. This affects an unknown part of the file /browse. The manipulation of the argument search/featured/recommended/skill leads to cross site scripting. It is possible to initiate the attack remotely. The associated identifier of this vulnerability is VDB-234423. 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 confidence

A reflected Cross-Site Scripting (XSS) vulnerability exists in the Mastery LMS 1.2 /browse endpoint. The search, featured, recommended, and skill parameters are not properly sanitized before being reflected in the web page, allowing injection of malicious JavaScript code via crafted URL parameters.

MitigationImplement proper input validation and output encoding for all user-supplied parameters in the /browse endpoint. Use context-aware escaping when rendering user input in HTML, and consider implementing a Content Security Policy (CSP) as a defense-in-depth measure.

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
Mastery LmsApplication
Affected:= 1.2

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Mastery LMS version
    Locate the installed version of Creativeitem Mastery LMS in your application (check admin panel, plugin files, or version.php)
    Affected if The installed version is 1.2 exactly
  2. Identify /browse endpoint availability
    Access your Mastery LMS installation and navigate to the /browse URL path, or check your web server logs for requests to this endpoint
    Affected if The /browse endpoint is accessible and responds to requests
  3. Test search parameter for XSS reflection
    Send a request to /browse with a benign XSS probe in the search parameter (such as <script>alert(1)</script> or <img src=x onerror=alert(1)>) and inspect the response body to see if the payload is rendered unescaped
    Affected if The search parameter value is reflected in the response without HTML encoding
  4. Test featured parameter for XSS reflection
    Send a request to /browse with a benign XSS probe in the featured parameter and inspect the response to check if the input is returned unescaped
    Affected if The featured parameter value is reflected in the response without HTML encoding
  5. Test recommended parameter for XSS reflection
    Send a request to /browse with a benign XSS probe in the recommended parameter and inspect the response for unescaped output
    Affected if The recommended parameter value is reflected in the response without HTML encoding
  6. Test skill parameter for XSS reflection
    Send a request to /browse with a benign XSS probe in the skill parameter and inspect the response to verify if output is properly escaped
    Affected if The skill parameter value is reflected in the response without HTML encoding

You are affected if Mastery LMS version 1.2 is installed AND the /browse endpoint is accessible AND any of the search, featured, recommended, or skill parameters reflect unescaped input in the response.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding for all user-supplied parameters in the /browse endpoint. Use context-aware escaping when rendering user input in HTML, and consider implementing a Content Security Policy (CSP) as a defense-in-depth measure.

Fix this in Mastery Lms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-3753 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-3753 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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