Skip to content
medium Token Standards No SWC entry CWE-393

ERC-721/1155 Missing Receiver Validation (Safe Transfer)

SAFE-0054 Token Standards Checked automatically by the scanner
1

What goes wrong

Using transferFrom instead of safeTransferFrom (or skipping onERC721Received checks) can send NFTs to contracts that cannot handle them, permanently locking the asset; conversely, blindly trusting the hook re-enables reentrancy.

2

How to fix it

the pattern that is safe
nft.safeTransferFrom(address(this), to, id); // checks receiver; guard caller
◆
Use safe transfers but guard against hook reentrancy.
3

Related vulnerabilities in Token Standards

SAFE-0053Unsafe / Unprotected Minting critical · Token Standards SAFE-0051Missing SafeERC20 / Non-Standard Token Handling high · Token Standards SAFE-0052Fee-on-Transfer / Rebasing Token Accounting Mismatch high · Token Standards SAFE-0055Burn Authorization / Burn-From Missing Checks high · Token Standards SAFE-0107Fee-on-Transfer / Rebasing Token Mis-Accounting high · Token Standards SAFE-0208Non-Standard ERC20 Return Value Not Handled high · Token Standards SAFE-0050ERC-20 Approval Race Condition medium · Token Standards SAFE-0056EIP-2612 Permit Misuse / Front-Running medium · Token Standards
← PreviousUnsafe / Unprotected Minting
Check your own contract for this

The SaferICO scanner runs 201 detectors over your Solidity source, SAFE-0054 among them. Paste an address or the source itself — a small per-scan fee, shown before you sign, or unlimited on any plan.

Run the scanner See how it is attacked Read the docs