Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.1amended

LTI 1.3 Grade Pass Back Implementation has Missing Authorization Vulnerability

CVE-2023-23611GHSA-7j9p-67mm-5g87

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (lti-consumer-xblock 7.2.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
2.1 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2023-23611: 0.38% estimated exploitation activity in the next 30 days; percentile 32.50 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 resourcelinkid 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-7j9p-67mm-5g87

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-7j9p-67mm-5g87

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-23611

Advisory: LTI 1.3 Grade Pass Back Implementation has Missing Authorization Vulnerability
IDs: CVE-2023-23611, GHSA-7j9p-67mm-5g87
Record: https://patchnext.com/advisories/cve-2023-23611 (revision 3, source checked 26 Oct 2026, 13:16 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: lti-consumer-xblock 7.2.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI lti-consumer-xblock: affected >= 7.0.0, < 7.2.2; fixed in 7.2.2

## Suggested inspection (read-only)
- `python -m pip show lti-consumer-xblock`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on lti-consumer-xblock.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-7j9p-67mm-5g87 (OSV record GHSA-7j9p-67mm-5g87 lists affected ranges: PyPI lti-consumer-xblock >=7.0.0 <7.2.2 (fixed))
- Verified: https://github.com/advisories/GHSA-7j9p-67mm-5g87 (GitHub-reviewed advisory GHSA-7j9p-67mm-5g87 lists affected ranges: PyPI lti-consumer-xblock >=7.0.0 <7.2.2)

Commands are suggestions: review each one before running it.

Loading voting…