# CVE-2022-44631: WordPress 1app Business Forms Plugin <= 1.0.0 is vulnerable to Cross Site Scripting (XSS)

> Authenticated attackers with author privileges can inject malicious scripts via stored XSS in the 1app Business Forms plugin, potentially compromising user sessions.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Apr 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-cp7r-qm2p-wcq3

## What is CVE-2022-44631?

CVE-2022-44631 is a medium-severity cross-site scripting vulnerability in 1app Business Forms, published on 23 Apr 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Auth. (author+) Stored Cross-Site Scripting (XSS) vulnerability in 1app Technologies, Inc 1app Business Forms plugin <= 1.0.0 versions.

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

## Which versions are affected by CVE-2022-44631?

It affects 1 product.


Products: 1app 1app Business Forms.

## How do I fix CVE-2022-44631?

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

## Is CVE-2022-44631 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-44631 and fix it if it is affected.

What it is: CVE-2022-44631 is a medium-severity cross-site scripting vulnerability in 1app Business Forms, published on 23 Apr 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-44631 in the wild and no public exploit code.

Affected product: 1app Business Forms. 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-2022-44631/ (Markdown: https://insights.sbomify.com/CVE-2022-44631/index.md)
```

## Sources

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

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