JSON Hijacking (aka JavaScript Hijacking)

AttackPattern · CAPEC-111

Attributed source ↗ · Plaintext record · Complete record and assertions JSON

Inspect structured metadata and provenance

{
  "id": "CAPEC-111",
  "title": "JSON Hijacking (aka JavaScript Hijacking)",
  "type": "AttackPattern",
  "source_url": "https://capec.mitre.org/data/definitions/111.html",
  "snapshot": "capec.xml",
  "status": "Draft",
  "rights": "Source metadata only; source notices retained; no operational prose or payloads",
  "review_status": "machine-extracted; source-specific checks passed, editorial review pending",
  "abstraction": "Standard",
  "source_version": "3.9"
}

Explicit source assertions (3)

First 80 shown here; the complete set is in this record’s JSON and plaintext. Each relationship retains its source and locator. No inferred relationships are added.

CAPEC-111 → related_weakness → CWE-345

CAPEC: Catalog mapping; does not establish an incident or actor use

Assertion source · Locator: Attack_Pattern[@ID='111']/Related_Weaknesses

CAPEC-111 → related_weakness → CWE-346

CAPEC: Catalog mapping; does not establish an incident or actor use

Assertion source · Locator: Attack_Pattern[@ID='111']/Related_Weaknesses

CAPEC-111 → related_weakness → CWE-352

CAPEC: Catalog mapping; does not establish an incident or actor use

Assertion source · Locator: Attack_Pattern[@ID='111']/Related_Weaknesses

Provided as is, for information only, with no warranty and no liability. Not legal or professional advice. Security and radio material is for authorized, lawful use only. Full disclaimer.

Visits are logged on our own server: IP address, browser and device details, and pages viewed. We use them to understand traffic and spot attacks, and never share or sell them.