Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.cveplayground.com/llms.txt

Use this file to discover all available pages before exploring further.

​
About the platform

There is a free tier with full access to a rotating set of labs. The blog and the public profile pages are free for everybody, with no sign in. Pricing for the full catalog is at cveplayground.com.
No. A browser is enough. Some labs are easier if you have curl or your favourite HTTP client open in a terminal, but you can do every lab from a browser only.
A lab walks you through the bug in five steps and asks five multiple choice questions. A challenge gives you the same vulnerable app, asks you to find the flag, and offers no walkthrough. Labs teach. Challenges test. See guided labs and challenges for the longer version.

​
Accounts

To track XP, streaks, badges, and your patch log. Without an account, the platform has no way to remember what you have done, and the questions and the leaderboard would be meaningless.
The sign in goes through Auth0, so whatever Auth0 accepts is fine.
Not from the UI today. The handle is used in URLs, on the leaderboard, and on first blood records, and rewriting all of that on a handle change is risky. If you really need to change it, contact support and they can do it manually. Display name is changeable any time in settings.
Auth0 has your identity data (email, social login). The platform stores your handle, answers, XP, badges, and the heatmap. Sentry and Microsoft Clarity see anonymised error and session data when those services are enabled. Nothing else.

​
Labs and questions

The explanation appears after you answer, right or wrong. If you want to read the explanation again later, the question card stays open with your prior verdict; you can come back any time. The platform does not publish an answer key separately, because the explanations are the answer key.
Send the CVE ID and the question number to contact@cveplayground.com. Question content is reviewed and updated when issues come in.
Yes. The lab is always available. Re-answering correctly does not award XP again, but you can revisit any time to refresh your memory.
The brief, locate, and reproduce sections are effectively hints. If you cannot reproduce the bug, the reproduce section walks you through it. If you cannot read the patch, the patch section explains it. The five questions are the only place where there are no hints.

​
Sandboxes

The exact budget is shown on the sandbox card while one is running. If you stop using a sandbox without stopping it, it may expire automatically.
The vulnerable application, any dependencies it needs to run (a database, a cache, downstream services), and nothing else. No real user data. No network access beyond what the lab requires.

​
Researcher questions

Yes. Every lab is tied to a published CVE with a real advisory and a real patch. The platform does not invent vulnerabilities.
The lab team picks CVEs that are educational: well documented, with clear patches, and ideally with a public PoC or writeup. The labs then standardise the reproduction so it works inside a small container.
Yes. Send the CVE ID and a sentence on why it would make a good lab to contact@cveplayground.com. Not every CVE makes it; the lab team filters for ones that fit the format.
The patch step shows the upstream diff and links to the original commit when one is available. The lab team does not modify the patches; what you see is what the vendor shipped.

Troubleshooting

When something is broken.

Glossary

Terms used across the docs.