Happy Addons For ElementorWordPress extension · Wedevs
CVE-2023-28989
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in weDevs Happy Addons for Elementor plugin <= 3.8.2 versions.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in weDevs Happy Addons for Elementor plugin versions 3.8.2 and below. The vulnerability allows attackers to trick authenticated users into performing unintended actions via malicious requests, potentially leading to unauthorized configuration changes or data manipulation within the plugin settings.
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
Happy Addons For ElementorWordPress extension
< 3.8.3CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Check Happy Addons for Elementor versionIn WordPress admin, go to Plugins > Installed Plugins, find Happy Addons for Elementor, and note the version number displayed. Alternatively, check the plugin header in /wp-content/plugins/happy-addons-for-elementor/ or via WP-CLI: wp plugin list --name='happy-addons-for-elementor'Affected if The installed version is 3.8.2 or lower (any version below 3.8.3)
-
Confirm plugin is activeVerify the plugin status in WordPress admin Plugins page or via WP-CLI: wp plugin list --name='happy-addons-for-elementor' --status=activeAffected if The plugin is installed and active on the WordPress site
If Happy Addons for Elementor version 3.8.2 or below is installed and active, the environment is vulnerable to CVE-2023-28989 CSRF attacks.
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 · scoped3.8.3
Update Happy Addons for Elementor to the latest patched version. If no patch is available, implement anti-CSRF tokens (nonces) on all state-changing actions and validate the request origin.
Happy Addons for Elementor 3.8.3
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find "Happy Addons for Elementor" in the plugin list
- Check if an update is available (version should be 3.8.3 or later)
- If update available, click "Update Now" to upgrade to the fixed version
- After update completes, verify the plugin shows version 3.8.3 or newer
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Happy Addons For Elementor
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28989 — 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-2023-28989 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