Skip to content
Back to skills

Wstg Clnt 08

ASecurity

Testing for Cross-Site Flashing

  • 3,518 stars
  • 0 votes
  • 0 copies
  • 5 views
  • Added September 3, 2026
securityjavascriptrustgojavabashtesting

Works with

  • cli

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add CyberStrikeus/CyberStrike --skill wstg-clnt-08 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Wstg Clnt 08?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Wstg Clnt 08
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cyberstrikeus-wstg-clnt-08/badge)](https://www.skillsdirectory.com/skills/cyberstrikeus-wstg-clnt-08)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: wstg-clnt-08
description: "Testing for Cross-Site Flashing"
category: client-side
owasp_id: WSTG-CLNT-08
version: "1.0.0"
author: cyberstrike-official
tags: [client-side, javascript, dom, cors, wstg, clnt]
tech_stack: [html, javascript]
cwe_ids: [CWE-1021]
chains_with: []
prerequisites: []
severity_boost: {}
---

# wstg-clnt-08

## Test ID

WSTG-CLNT-08

## Test Name

Testing for Cross-Site Flashing

## High-Level Description

Cross-Site Flashing (XSF) vulnerabilities occur in Flash/SWF applications when user input is improperly handled. Although Flash is deprecated, legacy applications may still use it. Similar vulnerabilities can exist in other rich media technologies.

---

## What to Check

- [ ] Flash files on target site
- [ ] crossdomain.xml configuration
- [ ] External data loading in SWF
- [ ] User input in Flash parameters
- [ ] Legacy rich media content

---

## How to Test

### Step 1: Find Flash Content

```bash
#!/bin/bash
TARGET="target.com"

# Find SWF files
curl -s "https://$TARGET" | grep -oP '[^"]+\.swf'

# Check crossdomain.xml
curl -s "https://$TARGET/crossdomain.xml"

# Common paths
paths=("/crossdomain.xml" "/clientaccesspolicy.xml" "/flash/crossdomain.xml")
for path in "${paths[@]}"; do
    curl -s "https://$TARGET$path"
done
```

### Step 2: Analyze crossdomain.xml

```xml
<!-- Vulnerable configuration -->
<?xml version="1.0"?>
<cross-domain-policy>
    <allow-access-from domain="*"/>  <!-- VULNERABLE -->
</cross-domain-policy>

<!-- Secure configuration -->
<?xml version="1.0"?>
<cross-domain-policy>
    <allow-access-from domain="trusted.com"/>
    <allow-access-from domain="*.trusted.com"/>
</cross-domain-policy>
```

---

## Remediation

```xml
<!-- Restrict cross-domain access -->
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
    <site-control permitted-cross-domain-policies="master-only"/>
    <allow-access-from domain="www.trusted.com" secure="true"/>
</cross-domain-policy>
```

---

## Risk Assessment

| Finding                  | CVSS | Severity |
| ------------------------ | ---- | -------- |
| Wildcard crossdomain.xml | 5.3  | Medium   |
| XSF vulnerability        | 6.1  | Medium   |


---

## Checklist

```
[ ] Flash files identified
[ ] crossdomain.xml analyzed
[ ] SWF parameters tested
[ ] clientaccesspolicy.xml checked
[ ] Findings documented
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in security →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.