CVE-2022-46101: AyaCMS v3.1.2 was found to have a code flaw in the ust_sql.inc.php file, which allows attackers to cause comma

This month

HIGH 8.8DOWNGRADE

CVE-2022-46101 is a high-severity flaw (CVSS 8.8) affecting ayacms. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	2.1% (top 18%)
CISA exploited list	No
Weakness	CWE-94
Published	2022-12-22
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: ayacms project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-12-22 18:15 UTCPublished CVE record published
2026-06-17 05:11 UTCUpdated Record last modified

ayacms project ayacms DOWNGRADE

Affected: 3.1.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.1.2

1. Check installed version

apt-cache policy ayacms || rpm -q ayacms || ayacms --version

2. No fixed release: DOWNGRADE to a release before 3.1.2 (Debian / Ubuntu)

apt-cache madison ayacms sudo apt install ayacms=<VERSION_BEFORE_3.1.2> sudo apt-mark hold ayacms

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list ayacms sudo dnf downgrade ayacms-<VERSION_BEFORE_3.1.2> sudo dnf versionlock add ayacms

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-46101?

ayacms: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-46101 being exploited?

CVE-2022-46101 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-46101 affect?

CVE-2022-46101 affects ayacms. Severity is high (CVSS 8.8). 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.

How urgent is CVE-2022-46101?

Priority 56/100. High severity; Public exploit reference

Software pages

PHP vulnerabilities

Related CVEs

CVE-2022-48116 HIGH 7.2 DOWNGRADE AyaCMS v3.1.2 was discovered to contain a remote code execution (RCE) vulnerability via the component /admin/t
CVE-2022-47926 CRITICAL 9.8 DOWNGRADE AyaCMS 3.1.2 is vulnerable to file deletion via /aya/module/admin/fst_del.inc.php
CVE-2022-46102 CRITICAL 9.8 DOWNGRADE AyaCMS 3.1.2 is vulnerable to Arbitrary file upload via /aya/module/admin/fst_down.inc.php
CVE-2022-45550 CRITICAL 9.8 DOWNGRADE AyaCMS 3.1.2 is vulnerable to Remote Code Execution (RCE).
CVE-2022-45548 HIGH 8.8 DOWNGRADE AyaCMS v3.1.2 has an Arbitrary File Upload vulnerability.

References

← Back to latest CVEs