LiveActive security incident?Get immediate response
CVE Record

CVE-2022-35569: Blogifier v3.0 was discovered to contain an arbitrary file upload vulnerability at /api/storage/upload/Post...

Blogifier v3.0 was discovered to contain an arbitrary file upload vulnerability at /api/storage/upload/PostImage. This vulnerability allows attackers to execute arbitrary web scripts or HTML via a crafted file.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Blogifier v3.0 has a reported unsafe upload endpoint that can accept crafted files capable of running web scripts or HTML. For a business, the main concern is compromise of visitors or administrators through malicious content served by the site. The sources do not provide CVSS, fix details, or evidence of active exploitation.

Executive priority

Treat this as a time-bound exposure review, not a confirmed emergency. Prioritize systems that are public-facing, accept uploads, or support authenticated content authors. Escalate if Blogifier v3.0 is confirmed in production and the upload endpoint is reachable.

Technical view

The CVE describes an arbitrary file upload issue in Blogifier v3.0 at /api/storage/upload/PostImage. The reported impact is execution of arbitrary web scripts or HTML via a crafted file. Available source data does not confirm authentication requirements, affected deployment configurations, exploit maturity, or a patched version.

Likely exposure

Exposure is likely limited to deployments running Blogifier v3.0 with the PostImage upload API reachable. The source bundle lists affected vendor and product fields as n/a, so validate against installed software names, versions, and route availability.

Exploitation context

CISA KEV status is false in the source bundle. The provided sources do not report active exploitation. The GitHub issue reference is the only vulnerability-specific public reference supplied, so operational risk depends on whether the upload endpoint is exposed and trusted users can upload content.

Researcher notes

Evidence is sparse: no CVSS vector, CWE, exploit status, authentication context, or patched version appears in the source bundle. The most defensible classification is arbitrary file upload leading to script or HTML execution, with impact likely tied to stored malicious content served by Blogifier.

Mitigation direction

  • Check Blogifier project guidance for a fixed release or official remediation.
  • If still on Blogifier v3.0, prioritize migration or vendor-supported upgrade planning.
  • Restrict access to the PostImage upload endpoint where business workflows allow.
  • Review upload handling controls for file type, content, and storage location.
  • Monitor web logs for unexpected uploads to the PostImage endpoint.

Validation and detection

  • Inventory internet-facing and internal sites for Blogifier v3.0.
  • Confirm whether /api/storage/upload/PostImage exists and is reachable.
  • Review application logs for suspicious PostImage upload activity.
  • Inspect uploaded media storage for unexpected HTML or script-capable files.
  • Verify any remediation against vendor guidance before closing the finding.
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

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-2022-35569 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.

Source materials

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.