Back to skill

Security audit

Build Amazon Affiliate Plugin

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent Amazon affiliate WordPress plugin generator, with review-worthy but disclosed behavior around ad insertion, API credentials, and build dependencies.

Install or use this skill only for a WordPress Amazon Associates workflow you control. Before running generated code, change the hard-coded output directory to your project workspace, update the Gutenberg npm dependencies, and treat PA-API keys as sensitive secrets stored only in a properly secured WordPress admin environment.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (14)

Known Vulnerable Dependency: @babel/plugin-transform-modules-systemjs==7.29.0 — 1 advisory(ies): CVE-2026-44728 (@babel/plugin-transform-modules-systemjs generates arbitrary code when compiling)

High
Category
Supply Chain
Confidence
92% confidence
Finding

@babel/plugin-transform-modules-systemjs 7.29.0 is identified as generating arbitrary code when compiling, which is a serious supply-chain/build-chain risk. If untrusted code is ever passed through this transformer in development, CI, or packaging, the produced output could embed attacker-controlled behavior and later be shipped or executed.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: brace-expansion==1.1.12 — 4 advisory(ies): CVE-2026-13149 (brace-expansion: DoS via exponential-time expansion of consecutive non-expanding); CVE-2026-33750 (brace-expansion: Zero-step sequence causes process hang and memory exhaustion); CVE-2026-14257 (brace-expansion: DoS via unbounded expansion length causing an out-of-memory pro) +1 more

High
Category
Supply Chain
Confidence
89% confidence
Finding

brace-expansion 1.1.12 is associated with multiple denial-of-service conditions involving pathological brace patterns that can trigger excessive CPU or memory use. In this lockfile it appears in tooling/transitive dependencies, so risk is mainly to developer tools, CI jobs, or any build step that evaluates attacker-influenced glob patterns rather than to end users directly.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: js-yaml==4.1.1 — 4 advisory(ies): CVE-2026-84375 (js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources); CVE-2026-59869 (js-yaml: YAML merge-key chains can force quadratic CPU consumption); GHSA-5p4m-2wfm-xmqj (JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026) +1 more

High
Category
Supply Chain
Confidence
90% confidence
Finding

js-yaml 4.1.1 has reported quadratic or excessive CPU consumption issues when parsing crafted YAML structures. Although this file is only a lockfile and the package is part of tooling, any developer or CI process that parses untrusted YAML could be forced into resource exhaustion.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: picomatch==4.0.3 — 2 advisory(ies): CVE-2026-33672 (Picomatch: Method Injection in POSIX Character Classes causes incorrect Glob Mat); CVE-2026-33671 (Picomatch has a ReDoS vulnerability via extglob quantifiers)

High
Category
Supply Chain
Confidence
86% confidence
Finding

picomatch 4.0.3 is flagged for ReDoS and method-injection-related glob matching issues. In this context it is part of development tooling, so the primary exposure is malicious filenames or attacker-controlled glob patterns causing CI or local tooling slowdowns or incorrect matching behavior.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: tar-fs==3.0.4 — 3 advisory(ies): CVE-2025-48387 (tar-fs can extract outside the specified dir with a specific tarball); CVE-2024-12905 (tar-fs Vulnerable to Link Following and Path Traversal via Extracting a Crafted ); CVE-2025-59343 (tar-fs has a symlink validation bypass if destination directory is predictable w)

High
Category
Supply Chain
Confidence
94% confidence
Finding

tar-fs 3.0.4 has multiple path traversal and symlink-related extraction flaws that can write outside the intended destination when handling crafted tar archives. Even though it is a transitive dev dependency, this becomes high risk anywhere the build/test/tooling stack downloads or extracts archives from external or semi-trusted sources, because it can overwrite files on the developer machine or CI runner.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

This plain-text README describes behavior that automatically detects affiliate links and displays or replaces content with ads, and it mentions optional PA-API integration for product data. However, it does not include a user-facing warning about automatic modification of post content or that external Amazon/API requests and configured credentials may be used, which is relevant to user data/system integrity for skill descriptions.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

This markdown file describes settings for paapi_access_key and paapi_secret_key, which are sensitive credentials, but it does not warn administrators about the sensitivity of these values, storage implications, or the need to protect them. Under the markdown-file criteria for SQP-2, credential-related behavior that could affect privacy or system integrity should be disclosed to users.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: @babel/core==7.29.0 — 1 advisory(ies): CVE-2026-49356 (@babel/core: Arbitrary File Read via sourceMappingURL Comment)

Low
Category
Supply Chain
Confidence
84% confidence
Finding

The lockfile pins @babel/core to 7.29.0, which is flagged for an arbitrary file read issue via sourceMappingURL processing. In this skill context it is a build-time/transpilation dependency rather than runtime application logic, so exploitation would generally require processing attacker-controlled source inputs during development or CI, making the practical impact lower but still real.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

Content

Scanner excerpt · assets/plugin/assets/blocks/package.json (reported line 11)May include surrounding context.

json
"start": "wp-scripts start"
  },
  "dependencies": {
    "@wordpress/block-editor": "^12.0.0",
    "@wordpress/blocks": "^12.0.0",
    "@wordpress/components": "^25.0.0",
    "@wordpress/element": "^3.0.0",

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

Content

Scanner excerpt · assets/plugin/assets/blocks/package.json (reported line 12)May include surrounding context.

json
},
  "dependencies": {
    "@wordpress/block-editor": "^12.0.0",
    "@wordpress/blocks": "^12.0.0",
    "@wordpress/components": "^25.0.0",
    "@wordpress/element": "^3.0.0",
    "@wordpress/i18n": "^4.0.0"

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

Content

Scanner excerpt · assets/plugin/assets/blocks/package.json (reported line 13)May include surrounding context.

json
"dependencies": {
    "@wordpress/block-editor": "^12.0.0",
    "@wordpress/blocks": "^12.0.0",
    "@wordpress/components": "^25.0.0",
    "@wordpress/element": "^3.0.0",
    "@wordpress/i18n": "^4.0.0"
  },

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

Content

Scanner excerpt · assets/plugin/assets/blocks/package.json (reported line 14)May include surrounding context.

json
"@wordpress/block-editor": "^12.0.0",
    "@wordpress/blocks": "^12.0.0",
    "@wordpress/components": "^25.0.0",
    "@wordpress/element": "^3.0.0",
    "@wordpress/i18n": "^4.0.0"
  },
  "devDependencies": {

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

Content

Scanner excerpt · assets/plugin/assets/blocks/package.json (reported line 15)May include surrounding context.

json
"@wordpress/blocks": "^12.0.0",
    "@wordpress/components": "^25.0.0",
    "@wordpress/element": "^3.0.0",
    "@wordpress/i18n": "^4.0.0"
  },
  "devDependencies": {
    "@wordpress/scripts": "^26.0.0"

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

Content

Scanner excerpt · assets/plugin/assets/blocks/package.json (reported line 18)May include surrounding context.

json
"@wordpress/i18n": "^4.0.0"
  },
  "devDependencies": {
    "@wordpress/scripts": "^26.0.0"
  }
}

Static analysis

Detected: suspicious.exposed_secret_literal

File appears to expose a hardcoded API secret or token.

Critical
Code
suspicious.exposed_secret_literal
Location
references/AMAZON_API.md:38