# CVE-2026-4246: ElementsKit Pro <= 4.10.1 - Unauthenticated Stored Cross-Site Scripting via 's' Parameter

> Unauthenticated attackers can inject arbitrary scripts via the Advanced Search REST endpoint, leading to stored XSS when users view popular keywords.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-pf34-qr6f-74hf

## What is CVE-2026-4246?

CVE-2026-4246 is a medium-severity cross-site scripting vulnerability in wpmet ElementsKit Pro, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The ElementsKit Pro plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 's' parameter of the Advanced Search REST endpoint in all versions up to, and including, 4.10.1 due to insufficient input sanitization and output escaping. The REST endpoint at /wp-json/elementskit/v1/advanced-search uses permission_callback set to __return_true, allowing unauthenticated access. Search terms are stored in the ekit_advanced_search_popular_keyword WordPress option via update_option(). While sanitize_text_field() is applied, it does not encode double quotes, and the stored keywords are rendered in HTML attributes via sprintf without esc_attr(), allowing attribute injection. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user triggers the "no results" popular keywords view on pages using the Advanced Search widget.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-4246?


## How do I fix CVE-2026-4246?

No fix has been published for CVE-2026-4246 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-4246 being exploited?

There is no known exploitation of CVE-2026-4246 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4246 and fix it if it is affected.

What it is: CVE-2026-4246 is a medium-severity cross-site scripting vulnerability in wpmet ElementsKit Pro, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-4246 in the wild and no public exploit code.

Affected product: wpmet ElementsKit Pro. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-4246/ (Markdown: https://insights.sbomify.com/CVE-2026-4246/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4246
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4246
- OSV: https://osv.dev/vulnerability/CVE-2026-4246

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-4246/
Summaries are generated and may contain mistakes; the official description above is the record.