# Signed action does not bind its intended context

A valid signature is accepted for another recipient, action, verifier or chain context contrary to the authorization contract.

**Candidate CWE:** [CWE-345](https://cwe.mitre.org/data/definitions/345.html)

## Test hypothesis

Generate a local baseline signature, then vary exactly one intended binding in a fresh local setup: recipient, amount, verifier instance or chain context. Compare recovered signer and accepted state change.

## Evidence required

Message schema, domain, differing context field, verifier logic and unintended local operation.

## Rule out false positives

Intentionally portable authorizations and unsupported signing paths require a demonstrated conflicting guarantee.

## Playbook and command references

- [Contract signatures and oracles: context, freshness and units](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/modules/contract-signatures-oracles.html) — Test signed-action context and price-consumer assumptions with local keys, mock feeds and explicit negative controls.
- [Authentication, recovery, federation, and session lifecycle](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/modules/identity-session.html) — Test registration, recovery, identity changes, invitations, SSO enforcement, and deprovisioning as one account state machine.

[Find the associated command snippets](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/commands.html?q=Contract%20signatures%20and%20oracles%3A%20context%2C%20freshness%20and%20units)

## Referenced by these target playbooks

[Web3 & protocols](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/web3.html) · [OSS & self-hosted](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/oss.html)

## Report checklist

- [ ] Capture the affected version, configuration, identities, and object ownership.
- [ ] Preserve a valid baseline and a negative control.
- [ ] Reproduce the forbidden data access, action, or state change on controlled fixtures.
- [ ] Explain the intended security rule and why the observed behavior violates it.
- [ ] State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.

## Conditional ATT&CK mapping

No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the [mapping guide](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/attack.html).

## Primary references

- [EIP-712](https://eips.ethereum.org/EIPS/eip-712)

[Back to the complete vulnerability catalog](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/vulnerabilities.html)