# CVE-2026-111021: Persian WooCommerce SMS 7.2.0 - 7.3.1 - Reflected XSS via 'pwsms_mobiles' Parameter


- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-j4v8-4289-whj4

## What is CVE-2026-111021?

CVE-2026-111021 is a high-severity vulnerability in Unknown افزونه پیامک ووکامرس | Persian WooCommerce SMS, published on 28 Oct 2026. 

### Official description

The افزونه پیامک ووکامرس | Persian WooCommerce SMS WordPress plugin before 7.3.2 does not sanitise and escape a parameter before reflecting it back into an HTML attribute, leading to Reflected Cross-Site Scripting that is executed in the browser session of a logged-in privileged user who is tricked into submitting a crafted cross-site request.

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

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


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

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

## Is CVE-2026-111021 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111021 is a high-severity vulnerability in Unknown افزونه پیامک ووکامرس | Persian WooCommerce SMS, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-111021 in the wild and no public exploit code.

Affected product: Unknown افزونه پیامک ووکامرس | Persian WooCommerce SMS. 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-111021/ (Markdown: https://insights.sbomify.com/CVE-2026-111021/index.md)
```

## Sources

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

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