CVE-2026-12732
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 · uneditedThe LearnPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'class_wrapper_form' shortcode attribute in versions up to, and including, 4.4.0. This is due to insufficient input sanitization and output escaping in the FilterCourseTemplate::sections() method at line 98, where the attacker-controlled attribute is inserted into an HTML class attribute via sprintf('<form class="%s">', $class_wrapper_form) without esc_attr() escaping. The FilterCourseShortcode::render() handler does not apply shortcode_atts() filtering, so raw user attributes flow directly through do_action('learn-press/filter-courses/layout', $data) into the template. 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 confidenceThe LearnPress WordPress plugin fails to sanitize the 'class_wrapper_form' shortcode attribute before using it in an HTML class attribute. The FilterCourseTemplate::sections() method at line 98 uses sprintf('<form class="%s">', $class_wrapper_form) without esc_attr() escaping, allowing authenticated contributors and above to inject arbitrary JavaScript via the shortcode.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm LearnPress plugin is installedIn WordPress admin, navigate to Plugins > Installed Plugins and locate LearnPress. Note the version number displayed.Affected if LearnPress is installed and active with a version prior to the patched release.
-
Identify usage of the FilterCourseTemplate shortcodeSearch your WordPress posts, pages, and custom post types for the presence of the [learn_press_filter_course] shortcode, specifically checking for the class_wrapper_form attribute.Affected if The shortcode is present with a custom class_wrapper_form value and the plugin version is unpatched.
-
Inspect the FilterCourseTemplate::sections() methodLocate the file containing FilterCourseTemplate class, typically in includes/class-filter-course.php or similar path. Navigate to the sections() method around line 98 and verify if sprintf() or printf uses the class_wrapper_form variable without esc_attr() wrapping.Affected if The code shows sprintf('<form class="%s">', $class_wrapper_form) without esc_attr() applied to $class_wrapper_form.
-
Check for shortcode_atts() filtering in render methodLocate the FilterCourseShortcode class and its render() method. Verify whether shortcode_atts() is called to filter raw user input for the class_wrapper_form attribute.Affected if shortcode_atts() is not used or does not sanitize the class_wrapper_form parameter before passing it to the template.
-
Assess user role exposureReview WordPress user roles and capabilities on your site. Determine if any users exist with Contributor-level access or higher who can create or edit content containing shortcodes.Affected if Authenticated users with Contributor role or above can create or edit content on the site.
You are affected if LearnPress is installed with an unpatched version and the FilterCourseTemplate shortcode with a custom class_wrapper_form attribute is in use, allowing any contributor-level user to inject malicious script.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply esc_attr() to the class_wrapper_form variable before embedding it in the HTML class attribute, and ensure FilterCourseShortcode::render() uses shortcode_atts() to filter raw user input. Update to version 4.4.1 or later when available.
LearnPress version 4.4.1 or later
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate the LearnPress plugin
- Check the current version number
- Upgrade to the latest available version of LearnPress (version 4.4.1 or higher)
- Verify the upgrade was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12732 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12732 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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