dbcve.org
TotaraApplication

CVE-2024-3931

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-18
Fix available
A fix is available. Upgrade to 13.46 / 14.38 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 was found in Totara LMS up to 18.7. It has been rated as problematic. Affected by this issue is some unknown functionality of the file admin/roles/check.php of the component User Selector. The manipulation of the argument ID Number leads to cross site scripting. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 13.46, 14.38, 15.33, 16.27, 17.21 and 18.8 is able to address this issue. It is recommended to upgrade the affected component.

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 confidence

Cross-site scripting (XSS) vulnerability in Totara LMS User Selector component (admin/roles/check.php) allows remote attackers to inject malicious scripts via the ID Number parameter.

MitigationUpgrade Totara LMS to version 13.46, 14.38, 15.33, 16.27, 17.21, or 18.8 or later to remediate this vulnerability.

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
TotaraApplication
Affected:>= 13.0, < 13.46>= 14.0, < 14.38>= 15.0, < 15.33>= 16.0, < 16.27>= 17.0, < 17.21>= 18.0, < 18.8

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
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Totara LMS version
    Locate the version.php file in your Totara installation directory (typically in /lib/ or the root directory) and read the $version variable, or use the admin interface under Site Administration > Server > Environment to view the installed version.
    Affected if The installed version falls within any of these ranges: 13.0 to 13.45, 14.0 to 14.37, 15.0 to 15.32, 16.0 to 16.26, 17.0 to 17.20, or 18.0 to 18.7
  2. Verify vulnerable component exists
    Check if the file admin/roles/check.php exists in your Totara web root directory.
    Affected if The file admin/roles/check.php is present on the server
  3. Confirm admin access is possible
    Verify that administrative users can access the roles management area by navigating to Site Administration > Users > Roles > Check role permissions, or confirm the URL path /admin/roles/check.php is accessible.
    Affected if Administrative users have access to the roles checking functionality
  4. Check ID Number field accessibility
    In the Totara admin interface, navigate to the role checking page and determine if the ID Number field can be populated with custom input.
    Affected if Users with admin access can input values into the ID Number parameter on the check.php page

Your Totara LMS installation is affected if the installed version is within the vulnerable ranges AND the admin/roles/check.php component is accessible to users.

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.

dbcve · scoped
Upgrade available Upgrade to 13.46 / 14.38 / 15.33 or later
Fixed in 13.4614.3815.33
Interim mitigation

Upgrade Totara LMS to version 13.46, 14.38, 15.33, 16.27, 17.21, or 18.8 or later to remediate this vulnerability.

Recommended fix High confidence

13.46, 14.38, 15.33, 16.27, 17.21, or 18.8 (select the version matching your current major release branch)

  1. Backup your Totara database and all site files before proceeding
  2. Enable maintenance mode on your Totara site via Site administration > Server > Maintenance mode
  3. Download the appropriate Totara version upgrade (13.46, 14.38, 15.33, 16.27, 17.21, or 18.8) from the Totara download portal
  4. Replace the existing Totara files with the new version files, preserving your config.php and any custom files
  5. Run the upgrade by accessing your Totara site URL - the upgrade script will automatically execute
  6. Clear all caches via Site administration > Development > Purge caches
  7. Disable maintenance mode
  8. Verify the User Selector functionality in admin/roles/check.php works correctly
Caveat Standard Totara upgrade risks apply - always test in staging first; ensure custom code/plugins are compatible with the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Totara Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3931 — 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-2024-3931 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