Security Patterns
Recurring security conditions linked to the case files, CWE classifications, and testing methods.
- Listed patterns
- 33
- Source
- Published case metadata
Published patterns
An administrative function returns genuine privileged content without requiring an authenticated session.
01 connected case PATTERN Broken Access ControlA server-side authorization boundary does not prevent an unauthorized client from reaching protected data or functionality.
05 connected cases PATTERN Build Manifest Route DisclosureA public client build manifest exposes routes or chunks that reveal otherwise undisclosed application structure.
01 connected case PATTERN Context-Specific Output Encoding FailureAttacker-controlled data is emitted without the encoding required by its exact HTML output context.
03 connected cases PATTERN Dangerous File UploadAn upload accepts a filename or file type that the web server can later execute or interpret unsafely.
01 connected case PATTERN Default Credential AuthenticationA 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 InjectionAn 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 MetadataA 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 ExposureA deployed artifact exposes a fixed credential or secret that is still accepted by its intended consumer.
02 connected cases PATTERN HTML Attribute InjectionUntrusted input escapes an existing HTML attribute value and creates attacker-controlled attributes on the rendered element.
01 connected case PATTERN Internal Endpoint ExposureAn endpoint described or intended as internal is reachable from the public application boundary.
05 connected cases PATTERN JSON Query Operator InjectionA 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 BypassA 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 InjectionA mail form passes user-controlled address text into mailer arguments, letting it change options rather than remain an address.
01 connected case PATTERN Missing AuthenticationA critical function is available without first establishing an authenticated user identity.
03 connected cases PATTERN Path TraversalUser-controlled path elements let a file operation reach outside the directory intended by the application.
01 connected case PATTERN PHP Object InjectionUntrusted PHP serialized data rebuilds application objects whose properties or magic methods can perform an unintended action.
01 connected case PATTERN postMessage Origin Validation FailureA 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 DisclosureProduction markup retains an operational comment that discloses sensitive implementation or routing information.
01 connected case PATTERN Public Backup ExposureBackup or migration artifacts remain retrievable from a publicly reachable web path.
02 connected cases PATTERN Public Metadata Route DisclosurePublic application metadata exposes an internal or otherwise unadvertised route together with enough context to prioritise focused validation.
01 connected case PATTERN Public Source Map DisclosureA production JavaScript source map is publicly retrievable and exposes embedded original source or security-relevant implementation contracts.
01 connected case PATTERN Reflected XSSRequest-controlled input is reflected into a generated page in a form that enables browser-side script execution.
01 connected case PATTERN Security MisconfigurationA deployment or server configuration exposes resources or behavior that the documented security boundary did not intend.
04 connected cases PATTERN Sensitive Configuration DisclosureA publicly reachable artifact reveals configuration values or operational secrets that should remain outside the public boundary.
06 connected cases PATTERN Sensitive Information DisclosureA public response reveals operational information beyond what the intended audience should receive.
10 connected cases PATTERN Server-Side Request ForgeryUser-controlled input changes where the application server sends an outbound request.
01 connected case PATTERN Server-Side Template InjectionAttacker-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 InjectionUntrusted input reaches a database query as executable SQL structure instead of remaining a bound data value.
05 connected cases PATTERN Stored XSSUser-controlled content is stored and later runs as script when another browser renders it.
02 connected cases PATTERN Template-to-Command ExecutionA server-side template injection reaches a callable operating-system primitive and returns dynamic command output.
01 connected case PATTERN Trusted Header Authentication BypassA 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 StorageStored password verification data uses a fast or insufficiently costly scheme that makes offline guessing inexpensive after disclosure.
01 connected case