dbcve.org
Xblock Lti ConsumerApplication · Openedx

CVE-2023-23611

MEDIUM · 5.4 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to 7.2.2 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
LTI Consumer XBlock implements the consumer side of the LTI specification enabling integration of third-party LTI provider tools. Versions 7.0.0 and above, prior to 7.2.2, are vulnerable to Missing Authorization. Any LTI tool that is integrated with on the Open edX platform can post a grade back for any LTI XBlock so long as it knows or can guess the block location for that XBlock. An LTI tool submits scores to the edX platform for line items. The code that uploads that score to the LMS grade tables determines which XBlock to upload the grades for by reading the resource_link_id field of the associated line item. The LTI tool may submit any value for the resource_link_id field, allowing a malicious LTI tool to submit scores for any LTI XBlock on the platform. The impact is a loss of integrity for LTI XBlock grades. This issue is patched in 7.2.2. No workarounds exist.

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

The LTI Consumer XBlock in Open edX lacks proper authorization checks when processing grade submissions. The code uses the resource_link_id field from line items to determine which XBlock to update with grades, but does not verify that the submitting LTI tool is the legitimate provider for that specific XBlock. This allows any integrated LTI tool to submit grades for any LTI XBlock by manipulating the resource_link_id value.

MitigationUpgrade LTI Consumer XBlock to version 7.2.2 or later, which includes authorization validation to ensure only the legitimate LTI tool can submit grades for its associated XBlock.

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
Xblock Lti ConsumerApplication
Affected:>= 7.0.0, < 7.2.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 LTI Consumer XBlock installation
    Run pip show xblock-lti-consumer or pip list | grep -i lti to locate the installed LTI Consumer XBlock package and note its version
    Affected if The package is installed with a version in the range >= 7.0.0 and < 7.2.2
  2. Verify installed version
    Compare the installed version number from step 1 against the affected range: versions 7.0.0 through 7.2.1 are vulnerable, version 7.2.2 and later are fixed
    Affected if The installed version is 7.0.0, 7.1.0, 7.1.1, 7.2.0, or 7.2.1 (any version >= 7.0.0 but < 7.2.2)
  3. Check if grade submission is configured
    Inspect the Open edX LTI XBlock settings or database for any LTI consumer configurations that enable grade passback/submission (look for enable_grade_updates or similar grade-related settings)
    Affected if Grade submission functionality is enabled and the vulnerable XBlock version is installed
  4. Identify active LTI tool configurations
    Review the LTI Consumer XBlock instances in the platform (via Django admin or XBlock configuration files) to see how many distinct LTI tools are integrated and which XBlocks use them
    Affected if Multiple LTI tools are configured and the vulnerable version is present, allowing one tool to potentially submit grades for another tool's XBlock

You are affected if the LTI Consumer XBlock is installed at version 7.0.0 through 7.2.1 and grade submission is enabled in your configuration.

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 7.2.2 or later
Fixed in 7.2.2
Interim mitigation

Upgrade LTI Consumer XBlock to version 7.2.2 or later, which includes authorization validation to ensure only the legitimate LTI tool can submit grades for its associated XBlock.

Recommended fix High confidence

7.2.2

  1. Identify the environment where the Xblock Lti Consumer is deployed (e.g., Open edX platform)
  2. Locate the requirements file or environment configuration that specifies the Xblock Lti Consumer version
  3. Update the version specification for xblock-lti-consumer to version 7.2.2 or later
  4. Run the appropriate package manager update command (e.g., pip install -U xblock-lti-consumer==7.2.2 or pip install xblock-lti-consumer>=7.2.2)
  5. Verify the installed version matches the expected patched version
  6. Restart any relevant services (such as the LMS or XBlock runtime) to ensure the new version is loaded
  7. Test that LTI grade submissions still function correctly for the intended use cases

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

Fix this in Xblock Lti Consumer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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