# CVE-2026-1263: Webling <= 3.9.0 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'title' Parameter

> Authenticated attackers can inject malicious scripts into Webling forms and memberlists, which execute when administrators view them.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **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:** 10 Apr 2026
- **Updated:** 10 Apr 2026
- **Also known as:** GHSA-983g-7xfg-6jxc

## What is CVE-2026-1263?

CVE-2026-1263 is a medium-severity cross-site scripting vulnerability in usystemsgmbh Webling, published on 10 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Webling plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 3.9.0 due to insufficient input sanitization, insufficient output escaping, and missing capabilities checks in the 'webling_admin_save_form' and 'webling_admin_save_memberlist' functions. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject Webling forms and memberlists with arbitrary web scripts that will execute whenever an administrator views the related form or memberlist area of the WordPress admin.

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

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


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

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

## Is CVE-2026-1263 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1263 is a medium-severity cross-site scripting vulnerability in usystemsgmbh Webling, published on 10 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1263 in the wild and no public exploit code.

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

## Sources

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

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