LiveActive security incident?Get immediate response
CVE Record

CVE-2021-33354: Directory Traversal vulnerability in htmly before 2.8.1 allows remote attackers to perform arbitrary file d...

Directory Traversal vulnerability in htmly before 2.8.1 allows remote attackers to perform arbitrary file deletions via modified file parameter.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-33354 affects HTMLy versions before 2.8.1. A logged-in attacker could manipulate a file parameter to delete files outside the intended directory. The main business risk is site disruption or integrity damage, not data theft. The provided sources do not show active exploitation.

Executive priority

Treat this as high priority for any internet-accessible HTMLy site with untrusted or broad user access. The likely impact is operational disruption or content damage through file deletion.

Technical view

The CVE describes a CWE-22 directory traversal flaw in HTMLy before 2.8.1. It is network-reachable, low-complexity, requires low privileges, and needs no user interaction. CVSS 3.1 is 8.1 with high integrity and availability impact and no confidentiality impact.

Likely exposure

Exposure is likely limited to organizations running HTMLy before 2.8.1 where an attacker can authenticate with low privileges. The source bundle provides no CPEs, deployment details, or affected configuration list.

Exploitation context

The CVE record says remote authenticated attackers can perform arbitrary file deletions using a modified file parameter. CISA KEV is false in the bundle, and no cited source claims exploitation in the wild.

Researcher notes

Evidence is sparse: the bundle includes the CVE description, CVSS vector, CWE-22, and one GitHub issue reference. It does not provide exploit maturity, CPEs, detailed affected configurations, or confirmed patch notes beyond the “before 2.8.1” version boundary.

Mitigation direction

  • Inventory HTMLy deployments and confirm exact version numbers.
  • Prioritize upgrading versions before 2.8.1 after checking vendor guidance.
  • Restrict administrative or content-management access to trusted users.
  • Review file permissions so the web process cannot delete unnecessary files.
  • Ensure recent backups are available and restoration is tested.

Validation and detection

  • Confirm whether any HTMLy instance is running below version 2.8.1.
  • Review authentication roles with access to file-handling features.
  • Check logs for unusual failed or unexpected file deletion activity.
  • Verify web server file permissions limit deletion scope.
  • Document findings against CVE-2021-33354 for remediation tracking.
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.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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

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-33354 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
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

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

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
2Source 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
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H2.85.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2021-33354Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

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-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.