LiveActive security incident?Get immediate response
CVE Record

CVE-2021-35290: File Upload vulnerability in balerocms-src 0.8.3 allows remote attackers to run arbitrary code via rich tex...

File Upload vulnerability in balerocms-src 0.8.3 allows remote attackers to run arbitrary code via rich text editor on /admin/main/mod-blog page.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-35290 reports that balerocms-src 0.8.3 can allow arbitrary code execution through a file upload path in the rich text editor on /admin/main/mod-blog. If a vulnerable deployment is reachable, this could become server compromise. Public sources do not provide CVSS, patch details, or confirmed active exploitation.

Executive priority

Treat this as a targeted high-priority check if BaleroCMS is in use. The likely asset population is narrow, but arbitrary code execution on a CMS can affect website integrity, hosted data, and server trust.

Technical view

The record describes a file upload vulnerability in balerocms-src 0.8.3 affecting the blog module rich text editor at /admin/main/mod-blog. The reported impact is remote arbitrary code execution. The source bundle does not identify CWE, CVSS metrics, authentication requirements, exploit maturity, or vendor remediation details.

Likely exposure

Likely exposure is limited to deployments of balerocms-src 0.8.3, especially where the admin blog editor or upload handling is reachable. The public record does not provide CPEs or broader affected product mapping.

Exploitation context

The CVE is not listed in KEV, and the provided sources do not show confirmed active exploitation. The impact claim is serious, but evidence is sparse and mainly references the CVE record and a GitHub issue.

Researcher notes

The public evidence is incomplete. Key unknowns include authentication requirement, exact upload validation failure, affected deployment configurations, and fixed version. Avoid assuming exploitability beyond balerocms-src 0.8.3 and the named admin blog editor route.

Mitigation direction

  • Check the project issue and repository for any maintainer-provided fix or upgrade guidance.
  • Restrict access to the admin interface to trusted administrators and trusted networks.
  • Review whether the rich text editor upload function can be disabled until guidance is confirmed.
  • Ensure uploaded files cannot be executed by the web server.
  • Back up the CMS and prepare rollback before applying any unverified community change.

Validation and detection

  • Inventory any balerocms-src deployments and confirm whether version 0.8.3 is present.
  • Determine whether /admin/main/mod-blog is reachable from untrusted networks.
  • Review recent uploads and server logs for unexpected executable content.
  • Confirm whether admin access controls and network restrictions are enforced.
  • Track the referenced GitHub issue for remediation or clarification from maintainers.
Prepared
Confidence
medium
Sources
3

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.

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
description · low confidence lookup

File 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 lookup
cve · low confidence lookup

CVE-2021-35290 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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