Platform

Platform overview How it works Authorization testing Evidence & reports Private scanning Integrations

Solutions

Security agencies Product teams Regulated industries Partner programme

Learn

Blog Knowledge hub Compare

Resources

Pricing Documentation Help centre FAQ Security & data What we haven’t proved

Company

About Contact Careers Sign in to the platform Start a $199 pilot →

Home / Help centre / Scan profiles

Scan profiles

What kinds of injection does the Injection class cover?

Quick answer

The Injection class covers SQL, NoSQL, command and template injection, plus XXE, SSTI and deserialisation. Cross-site scripting (Xss) and server-side request forgery (Ssrf) are separate classes, so you tick them on their own. Leave all classes unticked to cover all ten.

The short version

Injection means untrusted input ends up running as part of a command or query. The class in Cyberlop spans the server-side kinds, such as database and shell commands. Browser-side script injection and forged server requests sit in their own classes, so look there for those.

How it works in Cyberlop

These families come from the in-app documentation and belong to one specialist agent.

KindIn plain terms
SQL injectionInput changes a database query
NoSQL injectionThe same idea against document databases
Command injectionInput reaches the operating system shell
Template injection (SSTI)Input runs inside a page template
XXEA crafted XML file pulls in files or requests
DeserialisationCrafted data is rebuilt into live objects

That agent reads your code and writes hypotheses. Each one names an exact file and line, the missing defence and a claim you can test. That gives the next phase a clear target. If the exploitation phase is on, a later agent tries to prove each one against the running app. The finding then carries the payload, the request and the response.

Findings from this class get IDs that start with INJ, for example INJ-VULN-02. Short IDs like this are easy to quote in a ticket.

What to do next

Tick Injection in the Scope section of a profile. If you also want to cover browser-side script injection, tick Xss as well, and for forged server requests add Ssrf to the same profile, since each class has its own agent. A profile with no ticks covers all ten classes, so you only need to choose when you want a narrower run that finishes sooner.

Glossary entries explain the terms: SQL injection, NoSQL injection, command injection and XXE. To compare all classes, read which vulnerability classes Cyberlop tests. To set them, see how to pick vulnerability classes.

Full tutorial

Choose vulnerability classes in a Cyberlop scan profile

Step-by-step, with annotated screenshots.

Updated · Back to the help centre

Still stuck?

Tell us what you see on screen and an engineer will help you sort it out.