This describes a time-of-use issue, commonly associated with time-of-check to time-of-use race conditions. The key clue is that the user authenticates, but the unauthorized write operation occurs seconds later when the website is under heavy load. In a race condition, the application checks a security condition at one point in time but uses the result later, after the state may have changed. Heavy load can widen this timing gap and make exploitation more likely. CSRF tricks an authenticated user’s browser into submitting an unwanted request. SQLi injects malicious SQL into database queries. XSS injects scripts into web pages viewed by users. Because the issue is caused by timing between authentication and write execution, TOU is the best answer.

================