dbcve.org
The Pack Elementor AddonsWordPress extension · Webangon

CVE-2024-32785

MEDIUM · 6.1 CVSS v3.1 Published 2024-04-24
Fix available
A fix is available. Upgrade to 2.0.8.4 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 Webangon The Pack Elementor addons allows Cross-Site Scripting (XSS).This issue affects The Pack Elementor addons: from n/a through 2.0.8.3.

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

A CSRF vulnerability in Webangon's The Pack Elementor addons plugin (versions up to 2.0.8.3) allows attackers to inject XSS payloads through forged requests. An authenticated administrator visiting a malicious site can be tricked into executing crafted form submissions that store XSS in the plugin, which then executes when other users access the affected functionality.

MitigationImplement WordPress nonces on all form submissions and AJAX actions within the plugin, and verify these nonces server-side before processing any data. This prevents attackers from forging requests that could inject XSS content.

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
The Pack Elementor AddonsWordPress extension
Affected:< 2.0.8.4

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. Identify plugin installation
    Check the WordPress plugins directory or admin panel for 'Webangon The Pack Elementor Addons' and note the installed version number
    Affected if The plugin is installed with a version lower than 2.0.8.4 or no version is displayed (implying outdated)
  2. Verify plugin is active
    In WordPress admin, navigate to Plugins > Installed Plugins and confirm the plugin status is 'Active'
    Affected if The plugin is active and vulnerable to the CSRF attack vector
  3. Compare version to affected range
    Locate the version number in the plugin files (typically in the main PHP file header or readme.txt) and compare against 2.0.8.4
    Affected if The installed version is any version below 2.0.8.4 (versions up to and including 2.0.8.3)
  4. Inspect form actions for nonce presence
    Review plugin PHP files that handle form submissions or AJAX calls - look for 'wp_verify_nonce' or 'check_admin_referer' functions in form handling code
    Affected if Form handlers are found without nonce verification logic, indicating the CSRF protection is missing

A user is affected if the Webangon The Pack Elementor Addons plugin is installed, active, and running version 2.0.8.3 or lower without nonce verification on form submissions.

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

Implement WordPress nonces on all form submissions and AJAX actions within the plugin, and verify these nonces server-side before processing any data. This prevents attackers from forging requests that could inject XSS content.

Recommended fix High confidence

2.0.8.4

  1. Update The Pack Elementor Addons plugin to version 2.0.8.4 or later through the WordPress plugin repository or your site's plugin management interface
  2. After updating, verify the plugin version in the WordPress admin plugins list to confirm the upgrade was successful
  3. Review any plugin settings after upgrade to ensure configurations are intact

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

Fix this in The Pack Elementor Addons Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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