A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
The source closes with detailed examples for stored XSS, CSRF, and RCE. These cases are useful because the report structure stays recognizable while the exploitation conditions and impacts change. The right lesson is not to memorize the examples; it is to compare how evidence changes the description, impact, CVSS metrics, and proof of concept.
| Case | Core condition in the source | Reported severity |
|---|---|---|
| Stored XSS | Untrusted administrator-controlled filename data is reflected/stored and later rendered to other administrators. | CVSS 5.5 (Medium) |
| CSRF | A state-changing consumer registration request lacks anti-CSRF protection and can be triggered from a victim's active session. | CVSS 5.4 (Medium) |
| WebSphere deserialization RCE | Serialized data handling permits remote command execution on the affected application server. | CVSS 9.8 (Critical) |
The source's stored XSS example ties the vulnerability to an administrative workflow where an uploaded filename is reflected and stored without sufficient sanitization. Other administrators can encounter the stored value when viewing uploaded files. The report connects that behavior to browser-side script execution and then explains consequences such as credential theft, session impact, or redirection as potential attacker outcomes.
Report spine for the XSS caseTitle: Stored Cross-Site Scripting in the admin file workflowDescription: untrusted filename is stored and later renderedPOC: controlled input -> storage -> another admin views itImpact: affected administrator browser contextSeverity: justify each CVSS metric from the scenario
The important reporting pattern is causality: input reaches storage, storage reaches an administrative view, the browser interprets the untrusted content, and the security impact follows from the victim's privileges. Each step strengthens the next part of the report.
In the CSRF example, the source identifies a state-changing registration request without anti-CSRF protection. The proof of concept is framed around a victim who has an active session and is induced to visit a malicious page. The reported effect is the inadvertent creation of a fintech application using the victim's identity and privileges.
The RCE example is materially different. The source describes serialized Java objects carried in a base64-encoded form, identifies the presence of the 'rO0' header as an observation from the example, and explains that a crafted serialized object can trigger command execution on the affected server. The report then connects execution to the application's security context and rates confidentiality, integrity, and availability as High in the example.
These case studies come from an instructional source and are presented here as report-analysis examples. Apply the safety boundary from the course: reproduce security behavior only in systems you are explicitly authorized to test.
| Finding | What must be proven |
|---|---|
| Stored XSS | The malicious value can be stored and later interpreted in another administrator's browser context. |
| CSRF | A victim's authenticated session can be induced to perform the state-changing action without the required protection. |
| RCE | The crafted input reaches the vulnerable deserialization path and causes a controlled observable command execution in the authorized test context. |
The same report skeleton therefore produces different evidence. XSS depends on the browser rendering path, CSRF on cross-site state change under a victim session, and RCE on the server-side deserialization and execution chain. Strong reports adapt the proof to the mechanism instead of forcing every vulnerability into the same evidence shape.
Before submission, read your report as if you had never seen the application. Can you identify the affected component, reproduce the behavior, understand the security consequence, and trace the severity rationale back to evidence? The source's examples are effective because each report attempts to answer those questions explicitly.
Finish the lesson once you have worked through the material. This awards ★ 30 XP.