# CVE-2022-46101: Code injection in n/a

> Attackers can execute arbitrary code in AyaCMS via malicious input in the ust_sql.inc.php file, posing a critical risk to web application integrity.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 22 Dec 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-76w3-2xmj-8wr3

## What is CVE-2022-46101?

CVE-2022-46101 is a high-severity code injection vulnerability in n/a, published on 22 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

AyaCMS v3.1.2 was found to have a code flaw in the ust_sql.inc.php file, which allows attackers to cause command execution by inserting malicious code.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Ayacms Project Ayacms.

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

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

## Is CVE-2022-46101 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-46102](https://insights.sbomify.com/CVE-2022-46102/): File upload in n/a (critical 9.8)
- [CVE-2022-47926](https://insights.sbomify.com/CVE-2022-47926/): Path traversal in n/a (critical 9.8)
- [CVE-2022-45550](https://insights.sbomify.com/CVE-2022-45550/): Code injection in n/a (critical 9.8)
- [CVE-2022-43074](https://insights.sbomify.com/CVE-2022-43074/): File upload in n/a (critical 9.8)
- [CVE-2022-45548](https://insights.sbomify.com/CVE-2022-45548/): File upload in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-46101 is a high-severity code injection vulnerability in n/a, published on 22 Dec 2022. 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-46101 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-46101/ (Markdown: https://insights.sbomify.com/CVE-2022-46101/index.md)
```

## Sources

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

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