Skip to main content
No exploitation reportedFix available

CVE-2022-1064

No exploitation reported by the sources we read.

  • Published2022-03-25
  • Fixed in5.11.1
  • WeaknessCWE-89

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

SQL injection through marking blog comments on bulk as spam in GitHub repository forkcms/forkcms prior to 5.11.1.

Timeline

dates in UTC
  1. 2022-03-2512:15CVE publishedNVD

Versions per branch

NVD · OSV
Fork-cms fork cms
BranchAffectedFixed in
5.11< 5.11.15.11.1

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Fork-cms fork cms to 5.11.1

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVSS 3.18.8read 2026-10-23
  • CNACVSS 3.09known since 2026-10-23
  • NVDCVSS 2.06.5read 2026-10-23
  • CNAweakness (CWE)CWE-89known since 2026-10-23
  • NVDweakness (CWE)CWE-89read 2026-10-23
  • FIRST EPSSEPSS score1.2 %2026-11-18
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2022-03-30

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2022-03-25
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-rr8m-29g8-8cgc

Frequently asked questions

What is CVE-2022-1064?

SQL injection through marking blog comments on bulk as spam in GitHub repository forkcms/forkcms prior to 5.11.1.

Is CVE-2022-1064 actively exploited?

Active exploitation of CVE-2022-1064 has not been confirmed. Its EPSS score was 1.2% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-1064?

CVE-2022-1064 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running forkcms/forkcms? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record