# CVE-2026-97352: News Kit Addons For Elementor < 1.4.9 - Subscriber+ Plugin Installation and Activation via nekit_install_importer


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 24 Oct 2026
- **Also known as:** GHSA-qrph-gf2g-mv7f

## What is CVE-2026-97352?

CVE-2026-97352 is a medium-severity vulnerability in Unknown News Kit Addons For Elementor, published on 24 Oct 2026. 

### Official description

The News Kit Addons For Elementor WordPress plugin before 1.4.9 does not perform a capability check on one of its AJAX actions, allowing authenticated users with subscriber-level access and above to install and activate a specific News Kit Addons For Elementor WordPress plugin before 1.4.9 from the WordPress.org repository.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-97352 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97352 is a medium-severity vulnerability in Unknown News Kit Addons For Elementor, published on 24 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-97352 in the wild and no public exploit code.

Affected product: Unknown News Kit Addons For Elementor. 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-97352/ (Markdown: https://insights.sbomify.com/CVE-2026-97352/index.md)
```

## Sources

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

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