Parameter Tampering
Altering request fields to change application behavior or access.
What it is
An attack that modifies values a client sends (URL parameters, form fields, hidden inputs, headers, or cookies) to manipulate prices, identifiers, or logic the server wrongly trusts as fixed.
Why it matters
Trusting client-supplied values leads to fraud and unauthorized access, and tampered parameters often surface in logs as the mechanism behind a business-logic abuse or access-control break.
In practice
Editing a hidden price field at checkout to pay a fraction of the real amount.
What to look for
- Price, role or user ID fields changed in requests.
- Hidden form fields that the server trusts.
- Server responses that accept changed values.
Common mistake
Trusting values the server sent to the client. Recheck them on the server.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Email Header Analyzer
Walk the Received chain, and read the SPF, DKIM and DMARC verdicts.
- Phishing Case
A reported invoice email: pull the deciding values out of its raw headers, and say what they establish.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Burp Suite Commercial
An intercepting proxy for testing web apps by hand and with its scanner.
-
ZAP Open source
An open source web app scanner and proxy, often run in CI pipelines.
-
Cloudflare WAF Commercial
Blocks common web attacks at the edge while the code gets fixed.
Read next
- Input Validation: Checking that incoming data matches expected type, format, and range.
- Broken Access Control: Failure to enforce what authenticated users are allowed to do.
- Web Shell: A malicious script on a web server giving remote command access.