LiveActive security incident?Get immediate response
CVE Record

CVE-2022-45133: Mahara 21.10 before 21.10.6, 22.04 before 22.04.4, and 22.10 before 22.10.1 allows unsafe font upload for s...

Mahara 21.10 before 21.10.6, 22.04 before 22.04.4, and 22.10 before 22.10.1 allows unsafe font upload for skins. A particularly structured XML file could allow one to traverse the server to obtain access to secure files or cause code execution based on the payload.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-45133 affects Mahara versions before 21.10.6, 22.04.4, and 22.10.1. The issue is an unsafe font upload path for skins where a specially structured XML file could expose protected server files or potentially lead to code execution. Treat internet-facing Mahara systems as priority review items.

Executive priority

Schedule remediation in the next regular security maintenance window, sooner for public Mahara systems. The CVSS rating is medium, but possible secure-file access and payload-dependent code execution increase business impact if exposed.

Technical view

The CVE describes unsafe handling of font uploads for Mahara skins, mapped to CWE-26 path traversal. CVSS 3.1 is 6.5 with network access, low complexity, no privileges, and no user interaction. The public description indicates limited confidentiality and integrity impact, with potential code execution depending on payload.

Likely exposure

Exposure is most likely on Mahara deployments running 21.10.x before 21.10.6, 22.04.x before 22.04.4, or 22.10 before 22.10.1. Publicly reachable learning platforms have higher operational urgency.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The issue is remotely reachable by CVSS, but the bundle does not provide proof-of-concept status, exploit prevalence, or confirmed in-the-wild activity.

Researcher notes

Evidence is limited to the CVE description and linked Mahara/Launchpad references in the source bundle. Do not assume affected CPEs beyond the named Mahara versions. Validate by version and vendor guidance rather than offensive reproduction.

Mitigation direction

  • Upgrade affected Mahara 21.10 deployments to 21.10.6 or later.
  • Upgrade affected Mahara 22.04 deployments to 22.04.4 or later.
  • Upgrade affected Mahara 22.10 deployments to 22.10.1 or later.
  • Review Mahara forum and Launchpad guidance for deployment-specific notes.
  • Prioritize externally accessible Mahara systems for remediation.

Validation and detection

  • Inventory all Mahara instances and record exact versions.
  • Compare installed versions against the affected version ranges.
  • Confirm patched versions after maintenance or redeployment.
  • Review application and web logs for unexpected skin or font upload activity.
  • Check for unusual file access errors around upload handling.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-26: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-45133 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N3.92.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2022-45133Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-26 · source CWE mapping

Path Traversal: '/dir/../filename'

Path Traversal: '/dir/../filename' represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.