CVE-2022-0153: SQL Injection in GitHub repository forkcms/forkcms prior to 5.11.1.

Q: How do I fix CVE-2022-0153?

fork cms: upgrade to 5.11.1. Exact commands for each OS are on this page.

Q: Is CVE-2022-0153 being exploited?

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

Q: What does CVE-2022-0153 affect?

CVE-2022-0153 affects fork cms. Severity is high (CVSS 7.5). SQL Injection in GitHub repository forkcms/forkcms prior to 5.11.1.

Q: How urgent is CVE-2022-0153?

Priority 53/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

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

SQL Injection in GitHub repository forkcms/forkcms prior to 5.11.1.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.1% (top 34%)
CISA exploited list	No
Weakness	CWE-89
Published	2022-03-24
Last modified	2026-06-17

Publisher (CNA): huntr.dev · Vendor: fork-cms

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

Am I affected?

Timeline

2022-03-24 17:15 UTCPublished CVE record published
2026-06-17 04:20 UTCUpdated Record last modified

fork-cms fork cms UPGRADE

Affected: < 5.11.1

Fixed in: 5.11.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy fork-cms || rpm -q fork-cms || fork-cms --version

2. UPGRADE to 5.11.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade fork-cms

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade fork-cms

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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-0153?

fork cms: upgrade to 5.11.1. Exact commands for each OS are on this page.

Is CVE-2022-0153 being exploited?

CVE-2022-0153 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-0153 affect?

CVE-2022-0153 affects fork cms. Severity is high (CVSS 7.5). SQL Injection in GitHub repository forkcms/forkcms prior to 5.11.1.

How urgent is CVE-2022-0153?

Priority 53/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

GitHub vulnerabilities

Related CVEs

CVE-2020-24036 HIGH 8.8 UPGRADE PHP object injection in the Ajax endpoint of the backend in ForkCMS below version 5.8.3 allows an authenticate
CVE-2022-35590 MEDIUM 4.8 DOWNGRADE A cross-site scripting (XSS) issue in the ForkCMS version 5.9.3 allows remote attackers to inject JavaScript v
CVE-2022-35589 MEDIUM 4.8 DOWNGRADE A cross-site scripting (XSS) issue in the Fork version 5.9.3 allows remote attackers to inject JavaScript via
CVE-2022-35587 MEDIUM 4.8 DOWNGRADE A cross-site scripting (XSS) issue in the Fork version 5.9.3 allows remote attackers to inject JavaScript via
CVE-2022-35585 MEDIUM 4.8 DOWNGRADE A stored cross-site scripting (XSS) issue in the ForkCMS version 5.9.3 allows remote attackers to inject JavaS

References

← Back to latest CVEs