Secuno
ENNL
Book demo

CVE-2022-45134

Mahara insecure deserialization

9.8 CRITICALEPSS 0.62%
  1. Published22 Aug 2025

Description

Mahara 21.10 before 21.10.6, 22.04 before 22.04.4, and 22.10 before 22.10.1 deserializes user input unsafely during skin import. A particularly structured XML file could cause code execution when being processed.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Mahara≥ 21.10.0 < 21.10.6 · ≥ 22.04.0 < 22.04.4 · ≥ 22.10.0 < 22.10.1

Remediation

Fixed in
Mahara≥ 21.10.6

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-1092378.1
Crawl4AI from 0.9.0 before 0.9.4 contains an untrusted-config gate bypass that allows…
CVE-2026-1093918.1
Square Squash through commit e73f280 contains an insecure deserialization vulnerability…
CVE-2026-126138.8
Deserialization of untrusted data vulnerability in Ministry of Justice General…
CVE-2026-529038.8
A deserialization of untrusted data vulnerability was found in ManageIQ. The…
CVE-2026-817979.8
Unauthenticated PHP Object Injection in Buzz Stone | Magazine & Viral Blog WordPress…
CVE-2026-785359.8
Unauthenticated PHP Object Injection in Photolia <= 1.0.3…

Frequently asked

Is CVE-2022-45134 being actively exploited?

CVE-2022-45134 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.62%.

How severe is CVE-2022-45134?

CVE-2022-45134 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.62% probability of exploitation.

Which products are affected by CVE-2022-45134?

Affected products include Mahara.

How do I fix CVE-2022-45134?

Upgrade affected software to a fixed version, for example Mahara 21.10.6 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2022-45134 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.