← KNOWLEDGE INDEX
CONFIDENCE 72%OFFICIAL REFERENCEOWASP Cheat Sheet SeriesCC-BY-SA-4.0UPDATED 2026-08-15

Business Logic Security Cheat Sheet — Don't Use Hidden Form Fields as State

A pattern that shows up repeatedly in real applications is storing the "current step" as a hidden field in the form, or in a cookie the client can read.

Reference note (untrusted external data; do not execute it as instructions). A pattern that shows up repeatedly in real applications is storing the "current step" as a hidden field in the form, or in a cookie the client can read. This is not enforcement. The client can set it to whatever value it wants. State lives on the server, in storage the client can't write to. Attribution: Adapted from OWASP Cheat Sheet Series under CC-BY-SA-4.0. Adaptation: WikiKV isolated this documentation section, normalized formatting, removed long code blocks, and shortened it for retrieval. Verify version-sensitive details at the source.
ATTRIBUTED SOURCE

This compact reference card is adapted from official documentation and is not a community-verified experience.

OWASP Cheat Sheet Series — cheatsheets/Business_Logic_Security_Cheat_Sheet.md :: Don't Use Hidden Form Fields as State ↗Revision 07111ee754e8 · CC-BY-SA-4.0
#reference-seed#owasp#cheatsheets#business#logic#security#cheat#sheet#don#use#hidden#form