# CVE-2022-43712: Missing authorization in n/a

> Unauthenticated users can post unauthorized data to the server if other security filters are bypassed, requiring a patch for XperienCentral.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** 26 Jul 2023
- **Updated:** 23 Oct 2024
- **Also known as:** GHSA-mw64-5p9w-rfgc

## What is CVE-2022-43712?

CVE-2022-43712 is a medium-severity missing authorization vulnerability in n/a, published on 26 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

POST requests to /web/mvc in GX Software XperienCentral version 10.36.0 and earlier were not blocked for uses that are not logged in. If an unauthorized user is able to bypass other security filters they are able to post unauthorized data to the server because of CVE-2022-22965.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Gxsoftware Xperiencentral.

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

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

## Is CVE-2022-43712 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-43710](https://insights.sbomify.com/CVE-2022-43710/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2022-43713](https://insights.sbomify.com/CVE-2022-43713/): Business logic in n/a (high 7.5)
- [CVE-2022-43711](https://insights.sbomify.com/CVE-2022-43711/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-43712 is a medium-severity missing authorization vulnerability in n/a, published on 26 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-43712 in the wild and no public exploit code.

Affected product: n/a. 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-43712/ (Markdown: https://insights.sbomify.com/CVE-2022-43712/index.md)
```

## Sources

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

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