# CVE-2023-48763: WordPress JetFormBuilder plugin <= 3.1.4 - Content Injection vulnerability

> An attacker can inject malicious scripts via the JetFormBuilder plugin, potentially leading to code execution in the context of the web application.

- **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 Apr 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-xpj6-jg5q-m9x4

## What is CVE-2023-48763?

CVE-2023-48763 is a medium-severity cross-site scripting vulnerability in Crocoblock JetFormBuilder, published on 24 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS vulnerability in Crocoblock JetFormBuilder allows Code Injection.This issue affects JetFormBuilder: from n/a through 3.1.4.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

## Which versions are affected by CVE-2023-48763?


## How do I fix CVE-2023-48763?

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

## Is CVE-2023-48763 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-48763 and fix it if it is affected.

What it is: CVE-2023-48763 is a medium-severity cross-site scripting vulnerability in Crocoblock JetFormBuilder, published on 24 Apr 2024. 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-2023-48763 in the wild and no public exploit code.

Affected product: Crocoblock JetFormBuilder. 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-2023-48763/ (Markdown: https://insights.sbomify.com/CVE-2023-48763/index.md)
```

## Sources

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

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