dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-4333

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/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
The LearnPress – WordPress LMS Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'skin' attribute of the learn_press_courses shortcode in all versions up to and including 4.3.3. This is due to insufficient input sanitization and output escaping on the 'skin' shortcode attribute. The attribute value is used directly in an sprintf() call that generates HTML (class attribute and data-layout attribute) without any esc_attr() escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 LearnPress WordPress LMS plugin versions up to 4.3.3 contain a stored XSS vulnerability in the learn_press_courses shortcode. The 'skin' attribute value is used directly in sprintf() calls to generate HTML class and data-layout attributes without esc_attr() escaping, allowing authenticated attackers with Contributor-level access to inject arbitrary JavaScript that executes when users view affected pages.

MitigationUpdate LearnPress to a version beyond 4.3.3 once the patch is released. As a temporary measure, restrict or audit contributor-level user permissions and disable the learn_press_courses shortcode until the update is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 LearnPress plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate LearnPress. Note the version number displayed.
    Affected if LearnPress is not installed or is inactive - the vulnerability does not apply.
  2. Compare installed version to affected range
    Review the version number from the Plugins page. Compare it to the affected range: versions 4.3.3 and earlier are vulnerable.
    Affected if Installed version is 4.3.3 or lower - the plugin lacks the esc_attr() escaping fix for the skin parameter.
  3. Identify users with Contributor-level access
    Go to Users > All Users in WordPress admin. Review the role column to see which users have the Contributor role.
    Affected if No users with Contributor or higher roles exist - the attack vector requires authenticated access.
  4. Inspect the shortcode handler source code
    In the plugin files, locate the learn_press_courses shortcode handler (typically in includes/class-lp-shortcode.php or similar). Search for the 'skin' attribute handling. Verify whether esc_attr() is called when outputting the skin value into HTML class or data-layout attributes via sprintf().
    Affected if The code does NOT use esc_attr() when placing the skin value into HTML attributes - the XSS vulnerability is present.
  5. Check page source for unescaped output
    If you have a test page with a learn_press_courses shortcode using a skin attribute, view the page source. Search for the rendered course list container and inspect the class or data-layout attribute values.
    Affected if The skin value appears raw/unescaped in HTML attributes - this confirms the vulnerability is exploitable in your environment.

You are affected if LearnPress version 4.3.3 or lower is installed, Contributor-level users exist, and the shortcode handler does not use esc_attr() to sanitize the skin attribute before rendering it into HTML.

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

Update LearnPress to a version beyond 4.3.3 once the patch is released. As a temporary measure, restrict or audit contributor-level user permissions and disable the learn_press_courses shortcode until the update is applied.

Recommended fix Moderate confidence

LearnPress 4.3.4 or later

  1. Check the current installed version of the LearnPress plugin in WordPress admin under Plugins > Installed Plugins
  2. Navigate to Plugins > Add New > Upload Plugin or check for an update via the WordPress updates
  3. Update LearnPress to version 4.3.4 or later

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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