```
POC
```jsx
**
**
```
Mitigation
Use CORS Instead of JSONP
Strict Callback Validation
```php
"John Doe",
"email" => "john@example.com"
];
echo $callback . '(' . json_encode($data) . ');';
} else {
echo 'console.error("Invalid callback function.");';
}
```
JSONP Content-Type Validation
More Complex
#### Scenario 1: Exploiting with Malicious Parameters
```jsx
$name,
"email" => $email
];
// Vulnerable JSONP response with user input
echo $callback . '(' . json_encode($data) . ');';
```
exploit
```jsx
&email=attacker@example.com
```
get XSS and JSONP data
#### Scenario 2: Bypassing Weak Validation
```jsx
"John Doe",
"email" => "john@example.com"
];
echo $callback . '(' . json_encode($data) . ');';
} else {
echo 'console.error("Invalid callback function.");';
}
```
#### Exploit
```jsx
```
#### Scenario 4: JSONP Hijacking via CORS Misconfiguration
#### CORS-Enabled
```php
"58rec269qs4a9w8ewd2a6ghy6", // Sensitive data
];
echo $callback . '(' . json_encode($data) . ');';
```
Exploit
```javascript
```
Scenario 5: Advanced URL Manipulation
```php
"John Doe",
"email" => "john@example.com"
];
echo $callback . '(' . json_encode($data) . ');';
```
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://h3ckt0r.gitbook.io/0xsec/appsec/ewaptx/jsonp.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.