# CVE-2026-13712: Divi 5.0 - 5.8.1 - Contributor+ Stored XSS via Social Media Follow Skype URL

> Contributors can inject JavaScript via Skype URLs in Divi theme settings, leading to stored XSS against administrators.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-9jgc-73v6-9c3h

## What is CVE-2026-13712?

CVE-2026-13712 is a medium-severity cross-site scripting vulnerability in Unknown Divi, published on 16 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Divi WordPress theme before 5.9.0 does not properly escape some of its Social Media Follow module settings before outputting them in link attributes, allowing users with a role as low as contributor to store JavaScript which will run when a higher privileged user, such as an administrator, views the post.

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

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


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

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

## Is CVE-2026-13712 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-13712 is a medium-severity cross-site scripting vulnerability in Unknown Divi, published on 16 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13712 exists.

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

## Sources

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

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