Patterns from the cases

Security Patterns

Recurring security conditions linked to the case files, CWE classifications, and testing methods.

Listed patterns
33
Source
Published case metadata
Patterns found across the archive

Published patterns

33 indexed
PATTERN Anonymous Administrative Access

An administrative function returns genuine privileged content without requiring an authenticated session.

01 connected case
PATTERN Broken Access Control

A server-side authorization boundary does not prevent an unauthorized client from reaching protected data or functionality.

05 connected cases
PATTERN Build Manifest Route Disclosure

A public client build manifest exposes routes or chunks that reveal otherwise undisclosed application structure.

01 connected case
PATTERN Context-Specific Output Encoding Failure

Attacker-controlled data is emitted without the encoding required by its exact HTML output context.

03 connected cases
PATTERN Dangerous File Upload

An upload accepts a filename or file type that the web server can later execute or interpret unsafely.

01 connected case
PATTERN Default Credential Authentication

A login surface accepts a documented or predictable default credential and grants access that should require a deployment-specific secret.

01 connected case
PATTERN Error-Based Blind SQL Injection

An injected SQL predicate is converted into an observable error-versus-success response even though query output is not directly returned.

02 connected cases
PATTERN Exposed Version-Control Metadata

A deployed web root exposes repository metadata or object files that allow public recovery of source code or deployment history.

01 connected case
PATTERN Hard-Coded Credential Exposure

A deployed artifact exposes a fixed credential or secret that is still accepted by its intended consumer.

02 connected cases
PATTERN HTML Attribute Injection

Untrusted input escapes an existing HTML attribute value and creates attacker-controlled attributes on the rendered element.

01 connected case
PATTERN Internal Endpoint Exposure

An endpoint described or intended as internal is reachable from the public application boundary.

05 connected cases
PATTERN JSON Query Operator Injection

A JSON API accepts query operators or object-shaped filter values where the public client is expected to send simple data values.

01 connected case
PATTERN JWT Signature Verification Bypass

A server accepts JWT claims without requiring a valid signature, allowing a client to alter trusted identity or authorization data.

01 connected case
PATTERN Mailer Option Injection

A mail form passes user-controlled address text into mailer arguments, letting it change options rather than remain an address.

01 connected case
PATTERN Missing Authentication

A critical function is available without first establishing an authenticated user identity.

03 connected cases
PATTERN Path Traversal

User-controlled path elements let a file operation reach outside the directory intended by the application.

01 connected case
PATTERN PHP Object Injection

Untrusted PHP serialized data rebuilds application objects whose properties or magic methods can perform an unintended action.

01 connected case
PATTERN postMessage Origin Validation Failure

A message receiver accepts data from an untrusted browser origin or window because it does not validate event.origin and event.source.

01 connected case
PATTERN Production Comment Disclosure

Production markup retains an operational comment that discloses sensitive implementation or routing information.

01 connected case
PATTERN Public Backup Exposure

Backup or migration artifacts remain retrievable from a publicly reachable web path.

02 connected cases
PATTERN Public Metadata Route Disclosure

Public application metadata exposes an internal or otherwise unadvertised route together with enough context to prioritise focused validation.

01 connected case
PATTERN Public Source Map Disclosure

A production JavaScript source map is publicly retrievable and exposes embedded original source or security-relevant implementation contracts.

01 connected case
PATTERN Reflected XSS

Request-controlled input is reflected into a generated page in a form that enables browser-side script execution.

01 connected case
PATTERN Security Misconfiguration

A deployment or server configuration exposes resources or behavior that the documented security boundary did not intend.

04 connected cases
PATTERN Sensitive Configuration Disclosure

A publicly reachable artifact reveals configuration values or operational secrets that should remain outside the public boundary.

06 connected cases
PATTERN Sensitive Information Disclosure

A public response reveals operational information beyond what the intended audience should receive.

10 connected cases
PATTERN Server-Side Request Forgery

User-controlled input changes where the application server sends an outbound request.

01 connected case
PATTERN Server-Side Template Injection

Attacker-controlled content is compiled or evaluated as server-side template source instead of being passed to a fixed template strictly as data.

01 connected case
PATTERN SQL Injection

Untrusted input reaches a database query as executable SQL structure instead of remaining a bound data value.

05 connected cases
PATTERN Stored XSS

User-controlled content is stored and later runs as script when another browser renders it.

02 connected cases
PATTERN Template-to-Command Execution

A server-side template injection reaches a callable operating-system primitive and returns dynamic command output.

01 connected case
PATTERN Trusted Header Authentication Bypass

A backend trusts a client-reachable identity header that should only be set by an authenticated gateway or reverse proxy.

01 connected case
PATTERN Weak Password Storage

Stored password verification data uses a fast or insufficiently costly scheme that makes offline guessing inexpensive after disclosure.

01 connected case