Skip to content
WatchlistCritical

CVE-2022-26272Ionize Vulnerability

A remote code execution (RCE) vulnerability in Ionize v1.0.8.1 allows attackers to execute arbitrary code via a crafted string written to the file application/config/config.php.

Published Mar 24, 2022 · Updated Aug 12, 2026

Key Facts

Patch in the next maintenance window
  • CVE-2022-26272 is a critical-severity vulnerability (CVSS 9.8 v3.1) affecting Ionize (Ionizecms).
  • It is not listed in any known-exploited vulnerabilities catalog. No public exploit code is known.
  • EPSS estimates a 22% probability of exploitation in the next 30 days.
  • No fixed version is listed yet; check the vendor advisory for mitigations.
  • Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.

Scores

CVSS v3.1

9.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS (30-day exploit likelihood)

22%

Higher than 97.6% of all scored CVEs

Exploit maturity

Proof of concept

ATLAS score

39/100

Publication score, see How it works

Exploitation Verdict

KEV listed

Not listed

Federal due date

None

No federal due date

Ransomware use

Not reported

Attributed actors

None named

Exploit & Defence Guidance

Exploit maturity

Proof of concept

Public exploit code

1

Proof-of-concept links

In-the-wild evidence

0

Reports of active use

Description

A remote code execution (RCE) vulnerability in Ionize v1.0.8.1 allows attackers to execute arbitrary code via a crafted string written to the file application/config/config.php.

Affected Products

1 affected entries in total
ProductAffected versionsFixed in
IonizeIonizecms1.0.8.1n/a

Timeline

  1. Publicly disclosed

    Mar 24, 2022

  2. Last updated

    Aug 12, 2026

FAQ

Common Questions.

Is CVE-2022-26272 On Your Attack Surface?

Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.

Request A Demo

Figures as of Oct 19, 2026. Compiled by Brandefense technologies from public vulnerability catalogs; scoring as described in How it works.

To report an error, contact Brandefense.