dbcve.org
WebinarpressWordPress extension

CVE-2024-43339

MEDIUM · 6.1 CVSS v3.1 Published 2024-08-26
Fix available
A fix is available. Upgrade to 1.33.21 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in WebinarPress allows Cross-Site Scripting (XSS).This issue affects WebinarPress: from n/a through 1.33.20.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the WebinarPress WordPress plugin enables Stored Cross-Site Scripting (XSS). An unauthenticated attacker can trick a logged-in administrator into submitting a crafted request that stores malicious JavaScript in the plugin settings, which then executes in the browsers of other users viewing the affected content.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing forms and AJAX actions in WebinarPress, and ensure proper nonce verification on the server side before processing any user input that could be stored and reflected.

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
WebinarpressWordPress extension
Affected:< 1.33.21

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Verify WebinarPress plugin installation and version
    Navigate to WordPress admin > Plugins > Installed Plugins, locate 'Webinarpress Webinarpress' and note the version number displayed, or inspect the plugin header in /wp-content/plugins/webinarpress/includes/plugin.php for 'Version:' value
    Affected if The plugin is installed and the version number is less than 1.33.21
  2. Confirm plugin is active
    In WordPress admin > Plugins, verify the WebinarPress plugin shows as 'Active'
    Affected if The plugin is both installed (vulnerable version) AND active in the WordPress environment
  3. Inspect plugin settings for unauthorized script content
    Navigate to WebinarPress settings pages (WebinarPress > Settings, or any webinar management pages) and view the page source or inspect form fields for unexpected <script> tags, javascript: URIs, or event handler attributes (onload, onerror, onclick) in input fields
    Affected if Any plugin setting fields contain raw JavaScript code or HTML script tags that were not intentionally added by the administrator
  4. Check browser console for XSS execution in admin or public pages
    Visit the WordPress admin Dashboard while logged in, then visit any published webinar page as a logged-in user, and open browser developer console (F12) for JavaScript errors or unexpected script execution
    Affected if JavaScript code executes without being part of the page's legitimate source code, indicating stored XSS is present

A user is affected if WebinarPress plugin version less than 1.33.21 is installed and active in their WordPress environment, or if suspicious script tags are found in plugin configuration fields.

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

Implement anti-CSRF tokens (nonces) on all state-changing forms and AJAX actions in WebinarPress, and ensure proper nonce verification on the server side before processing any user input that could be stored and reflected.

Recommended fix High confidence

1.33.21 or later

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Find WebinarPress in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to the latest version
  5. 5. Alternatively, download version 1.33.21 or later from the WordPress plugin repository and upload/install it
  6. 6. Verify the update was successful by checking the plugin version

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

Fix this in Webinarpress 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-2024-43339 — 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-2024-43339 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