# CVE-2026-8617: Missing authorization in SearchPlus

> Unauthenticated attackers can modify or delete SearchPlus plugin settings due to missing authorization checks in AJAX handlers.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** GHSA-hrxf-7cvc-wf78

## What is CVE-2026-8617?

CVE-2026-8617 is a medium-severity missing authorization vulnerability in ailchev SearchPlus, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The SearchPlus plugin for WordPress is vulnerable to unauthorized modification and deletion of data in versions up to, and including, 1.7.1. This is due to a missing capability check and missing nonce validation on the searchplus_save_token_action_callback() and searchplus_reset_token_action_callback() functions, both of which are exposed to unauthenticated users through the wp_ajax_nopriv_ hooks. This makes it possible for unauthenticated attackers to overwrite or delete the plugin's stored account token and account name options (dym_token, dym_name, searchplus_token, searchplus_name, sp_token, sp_name).

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-8617 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8617 is a medium-severity missing authorization vulnerability in ailchev SearchPlus, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8617 in the wild and no public exploit code.

Affected product: ailchev SearchPlus. 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-8617/ (Markdown: https://insights.sbomify.com/CVE-2026-8617/index.md)
```

## Sources

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

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