LiveActive security incident?Get immediate response
CVE Record

CVE-2021-23682: Prototype Pollution

This affects the package litespeed.js before 0.3.12; the package appwrite/server-ce from 0.12.0 and before 0.12.2, before 0.11.1. When parsing the query string in the getJsonFromUrl function, the key that is set in the result object is not properly sanitized leading to a Prototype Pollution vulnerability.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw lets an attacker influence internal JavaScript object behavior through a crafted query string parsed by affected software. For exposed applications using vulnerable litespeed.js or Appwrite server-ce versions, the business risk is unauthorized data changes, limited data exposure, or service disruption depending on how polluted properties are later used.

Executive priority

Prioritize remediation for internet-facing Appwrite or services using litespeed.js. The vulnerability is high severity and remotely reachable, but current supplied evidence does not confirm active exploitation. Upgrade during the next urgent maintenance window, faster for exposed production systems.

Technical view

CVE-2021-23682 is prototype pollution in getJsonFromUrl query-string parsing. Keys assigned into the result object are not properly sanitized. Affected components are litespeed.js before 0.3.12 and appwrite/server-ce before fixed 0.11.1 or 0.12.2 releases. CVSS 3.1 is 7.3: network exploitable, low complexity, no privileges or user interaction.

Likely exposure

Exposure is most likely in internet-facing Node.js or Appwrite deployments that parse attacker-controlled URLs or query strings using affected code. Confirm package versions in dependency manifests, lockfiles, containers, and deployed Appwrite server-ce images.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. CVSS marks exploit code maturity as proof-of-concept. Treat this as remotely reachable where vulnerable parsing is exposed, but do not assume active exploitation without additional evidence.

Researcher notes

Focus on version confirmation and reachability of getJsonFromUrl with attacker-controlled query parameters. The core issue is missing key sanitization during object construction. Avoid assuming impact beyond CVSS without application-specific data flows showing polluted properties influence security decisions or service behavior.

Mitigation direction

  • Upgrade litespeed.js to 0.3.12 or later.
  • Upgrade Appwrite server-ce to fixed 0.11.1 or 0.12.2 releases as applicable.
  • Check vendor advisories and release notes before selecting branch-specific upgrades.
  • Restrict exposure of affected services until upgraded where feasible.
  • Review logs for suspicious query strings targeting object prototype keys.

Validation and detection

  • Inventory deployed litespeed.js and appwrite/server-ce versions.
  • Check package-lock, yarn.lock, composer files, and container image metadata.
  • Confirm affected routes parse user-controlled query strings through getJsonFromUrl.
  • Verify upgraded deployments no longer include vulnerable package versions.
  • Run regression tests around query parsing and URL handling.
Prepared
Confidence
high
Sources
8

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.

cve · low confidence lookup

CVE-2021-23682 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
7.3 (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:L/E:P

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
7Source 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
7.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P3.93.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2021-23682Attack 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:L/E:P

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/alitespeed.jsunspecifiedListed
n/aappwrite/server-ce0.12.0, unspecified, unspecifiedListed
Weakness

CWE details

No CWE listed

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