# CVE-2026-7503: code-projects for Plugin cstecgi.cgi setWiFiMultipleConfig buffer overflow

> Remote attackers can trigger a buffer overflow in the WiFi configuration handler to execute arbitrary code on affected IoT devices.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2026
- **Updated:** 4 May 2026
- **Also known as:** GHSA-f3fc-3r4q-r873

## What is CVE-2026-7503?

CVE-2026-7503 is a high-severity memory corruption vulnerability in code-projects for Plugin, published on 30 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was detected in code-projects for Plugin 4.1.2cu.5137. The impacted element is the function setWiFiMultipleConfig in the library /lib/cste_modules/wireless.so of the file /cgi-bin/cstecgi.cgi. The manipulation of the argument wepkey2 results in buffer overflow. The attack can be launched remotely. The exploit is now public and may be used.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-7503 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7503 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7503 is a high-severity memory corruption vulnerability in code-projects for Plugin, published on 30 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7503 exists.

Affected product: code-projects for Plugin. 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-7503/ (Markdown: https://insights.sbomify.com/CVE-2026-7503/index.md)
```

## Sources

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

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