Westmarch is a hiring platform. You are on the interview panel for candidate 8841, so you may view her scorecard. The PDF hides her salary expectation and the recruiter’s private notes.
The hiring committee also exports scorecards to a spreadsheet before each debrief.
One change to this request triggers the vulnerability. The challenge is to use your security intuition to work out what to change. Find the value the server shouldn’t trust, change it, and send it. The response tells you whether you were right.
Hint. Read the hidden salary expectation and recruiter note.
“Redacting sensitive fields in the PDF protects every version of the scorecard.”
Apply field-level authorization before rendering. Build one authorized scorecard object for the current user and pass it to both the PDF and CSV serializers. Keep the field policy in a shared service, restrict export endpoints by role, and add tests confirming every representation omits protected fields.
Check PDF and CSV exports, print views, JSON APIs, calendar feeds, admin downloads, and older API versions. Look for sensitive fields removed inside one template or serializer instead of by a shared authorization policy.
One Request Away is a daily series of challenges. They’re like code review, but for HTTP requests: in each one you’re one request away from triggering a vulnerability, and your goal is to identify what you need to change.