dbcve.org
ElementskitWordPress extension · Wpmet

CVE-2025-0321

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-28
Fix available
A fix is available. Upgrade to 3.7.9 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 ElementsKit Pro plugin for WordPress is vulnerable to DOM-Based Stored Cross-Site Scripting via the ‘url’ parameter in all versions up to, and including, 3.7.8 due to insufficient input sanitization and output 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 ElementsKit Pro WordPress plugin fails to properly sanitize and escape the 'url' parameter, allowing authenticated attackers with Contributor-level access to inject malicious JavaScript through stored XSS. This script executes whenever users access the affected page, enabling session hijacking, credential theft, or defacement.

MitigationUpdate ElementsKit Pro to version 3.7.9 or later to patch the vulnerability. Until updated, consider restricting contributor-level user permissions or temporarily disabling the affected plugin functionality.

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
ElementskitWordPress extension
Affected:< 3.7.9

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm ElementsKit Pro is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'ElementsKit' or check wp-content/plugins/elementskit directory exists
    Affected if ElementsKit Pro plugin is not present in the WordPress installation
  2. Identify the installed version
    In Plugins list, find the version number under ElementsKit. Alternatively, check the main plugin file header at wp-content/plugins/elementskit/elementskit.php for 'Version:' field
    Affected if Version is less than 3.7.9 (e.g., 3.7.8, 3.7.0, etc.)
  3. Check for contributor-level users
    Go to Users > All Users in WordPress admin and review the Role column, or query wp_usermeta table: SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%contributor%'
    Affected if Any user account has Contributor role or higher privileges exists on the site
  4. Identify usage of the vulnerable url parameter feature
    Review ElementsKit widget/element settings where a 'url' or link field accepts user input, particularly in widgets that allow custom links or button elements
    Affected if Site editors or contributors have access to create or edit pages using ElementsKit widgets with url/link fields

A site is affected if ElementsKit Pro version is below 3.7.9 AND contributor-level or higher users exist who can access the vulnerable url parameter feature in ElementsKit widgets.

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

Update ElementsKit Pro to version 3.7.9 or later to patch the vulnerability. Until updated, consider restricting contributor-level user permissions or temporarily disabling the affected plugin functionality.

Recommended fix High confidence

ElementsKit Pro 3.7.9

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the ElementsKit Pro plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 3.7.9 or later
  5. 5. Alternatively, download ElementsKit Pro version 3.7.9 or newer from the official source (wpmet.com)
  6. 6. Deactivate the current version of ElementsKit Pro
  7. 7. Delete the existing ElementsKit Pro plugin files
  8. 8. Upload and install the new version
Caveat Point releases typically do not introduce breaking changes; however, always test on a staging environment before applying to production

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

Fix this in Elementskit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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