LTI 1.3 Grade Pass Back Implementation has Missing Authorization Vulnerability (CVE-2023-23611) | HOL Guard CVE

Low · CVSS 3.7CVE-2023-23611GHSA-7J9P-67MM-5G87

LTI 1.3 Grade Pass Back Implementation has Missing Authorization Vulnerability

Answer in brief

CVE-2023-23611 records a Low severity (CVSS 3.7) vulnerability in LTI 1.3 Grade Pass Back Implementation has Missing Authorization Vulnerability. The current sources do not mark it as known exploited. The current feed maps lti-consumer-xblock (pypi). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 30, 2024Updated Sep 10, 2026Source checked Sep 10, 2026First seen by HOL Sep 10, 2026Material review Sep 10, 2026

Upstream Advisory

Key facts

Risk: Low · CVSS 3.7
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 3.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps lti-consumer-xblock (pypi). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
lti-consumer-xblockpypi	>=7.0.0 <7.2.2	7.2.2

Recommended response

Check inventory. Check lockfiles and deployed manifests for lti-consumer-xblock.
Review the reported fix. Update lti-consumer-xblock to 7.2.2 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 30, 2024
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Sep 10, 2026

Sources and claim methodology

Upstream source description

### Problem TL;DR: 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. In LTI 1.3, LTI tools can "pass back" scores that learners earn while using LTI tools to the edX platform. The edX platform then stores those LTI scores in a separate table. If the right conditions are met, these scores are then persisted to the LMS grades tables. LTI tools can create what are called "line items" on the edX platform. A line item can be thought of as a column in a grade book; it stores results for a specific activity (i.e. XBlock) for a specific set of users (i.e. users in the course using the XBlock). A line item has an optional resource_link_id field, which is basically the XBlock location. An LTI tool can supply any value for this field. 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. Because the LTI tool could have submitted any value for the resource_link_id field, this introduces the potential for a nefarious LTI tool to submit scores for any LTI XBlock on the platform. ### Impact 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 the resource_link_id (i.e. block location) for that XBlock. The impact is a loss of integrity for LTI XBlock grades. ### Patches No available patch ### Workarounds No

Quoted source text, attributed separately from HOL analysis.