Security readout for executives and security teams
Plain-English summary
CVE-2021-35369 is an arbitrary file read issue reported in Peacexie ImCat v5.2. The public record says it was fixed in v5.4 and could allow attackers to obtain sensitive information through the filtering_get_contents function. Severity and scoring are not provided, so business urgency depends on whether ImCat v5.2 is deployed.
Executive priority
Treat this as a targeted remediation item if ImCat is present. Prioritize version discovery first; upgrade confirmed v5.2 systems because the issue concerns sensitive file disclosure.
Technical view
The CVE describes a CWE-125-style arbitrary file read in ImCat v5.2 involving filtering_get_contents. The available source bundle does not provide CVSS, affected CPEs, detailed prerequisites, or exploit maturity. The only remediation detail provided is that v5.4 fixed the issue.
Likely exposure
Exposure is most likely limited to organizations running Peacexie ImCat v5.2. The source bundle does not identify affected CPEs, deployment conditions, vulnerable routes, or whether authentication is required.
Exploitation context
The CVE is not listed as KEV in the provided bundle. No cited source confirms active exploitation. A public GitHub issue exists, but the bundle does not establish exploitation in the wild or provide reliable severity context.
Researcher notes
Evidence is sparse. The CVE states the vulnerable function and fixed version, but not attack prerequisites, endpoint details, authentication state, or CVSS. Avoid assuming broader product impact beyond Peacexie ImCat v5.2 without vendor confirmation.
Mitigation direction
- Identify any Peacexie ImCat deployments and record their versions.
- Upgrade ImCat v5.2 deployments to v5.4 or later.
- Review the linked project issue and vendor guidance for scope details.
- Limit public exposure of ImCat where business use permits.
Validation and detection
- Confirm whether asset inventory contains Peacexie ImCat v5.2.
- Verify upgraded systems report ImCat v5.4 or later.
- Check application ownership records for unmanaged ImCat instances.
- Review logs for unusual sensitive file access patterns.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-125: 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 lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-35369 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/peacexie/imcat/issues/7CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.