@zerothreatai/vulnerability-registry 4.0.0 → 5.0.0

package/dist/categories/ssrf.js

@@ -6,7 +6,7 @@
 import { VulnerabilityCode } from '../error-codes.js';
 export const SSRF_VULNERABILITIES = {
     [VulnerabilityCode.SSRF_CLOUD_METADATA]: {
-        id: 46,
+        id: 450,
         code: VulnerabilityCode.SSRF_CLOUD_METADATA,
         title: 'Server-Side Request Forgery - Cloud Metadata Access',
         description: 'Critical SSRF vulnerability enabling access to cloud provider metadata services (AWS IMDSv1, GCP, Azure) which expose sensitive information including IAM credentials, API tokens, and instance configuration that can lead to full cloud account compromise and lateral movement.',
@@ -28,7 +28,7 @@ export const SSRF_VULNERABILITIES = {
         remediation: 'Block access to cloud metadata IP ranges (169.254.169.254). Implement IMDSv2 which requires tokens. Use allowlist for external URLs. Validate and sanitize all URL inputs.',
     },
     [VulnerabilityCode.SSRF_INTERNAL_SERVICE]: {
-        id: 47,
+        id: 451,
         code: VulnerabilityCode.SSRF_INTERNAL_SERVICE,
         title: 'Server-Side Request Forgery - Internal Service Access',
         description: 'SSRF vulnerability allowing attackers to access internal network services that should not be reachable from the internet, including databases, admin panels, cache servers, and other infrastructure components protected only by network segmentation without authentication.',
@@ -50,7 +50,7 @@ export const SSRF_VULNERABILITIES = {
         remediation: 'Implement URL allowlist for permitted external resources. Block requests to private IP ranges and localhost. Use network segmentation with proper authentication for internal services.',
     },
     [VulnerabilityCode.SSRF_PROTOCOL_SMUGGLING]: {
-        id: 48,
+        id: 452,
         code: VulnerabilityCode.SSRF_PROTOCOL_SMUGGLING,
         title: 'Server-Side Request Forgery - Protocol Smuggling',
         description: 'SSRF vulnerability exploiting non-HTTP protocol handlers like file://, gopher://, dict://, or ftp:// to read local files, interact with internal services using raw TCP, or perform attacks that would not be possible through HTTP requests alone, significantly expanding impact scope.',
@@ -72,7 +72,7 @@ export const SSRF_VULNERABILITIES = {
         remediation: 'Enforce HTTP/HTTPS only for outbound requests. Disable or block dangerous protocol handlers at the application and network level. Validate URL schemes against strict allowlist.',
     },
     [VulnerabilityCode.SSRF_BLIND_OOB]: {
-        id: 49,
+        id: 453,
         code: VulnerabilityCode.SSRF_BLIND_OOB,
         title: 'Server-Side Request Forgery - Blind OOB',
         description: 'Blind SSRF vulnerability confirmed through out-of-band DNS or HTTP callbacks indicating the server makes requests to attacker-controlled destinations even though responses are not reflected, enabling internal network scanning and data exfiltration through DNS or timing side channels.',
@@ -97,7 +97,7 @@ export const SSRF_VULNERABILITIES = {
     // OPEN REDIRECT
     // ========================================
     [VulnerabilityCode.REDIRECT_HEADER_INJECTION]: {
-        id: 50,
+        id: 454,
         code: VulnerabilityCode.REDIRECT_HEADER_INJECTION,
         title: 'Open Redirect - HTTP Header Injection',
         description: 'Open redirect vulnerability through Location header manipulation allowing attackers to redirect victims to malicious websites after authenticating or interacting with the legitimate application, facilitating phishing attacks that abuse user trust in the original domain.',
@@ -119,7 +119,7 @@ export const SSRF_VULNERABILITIES = {
         remediation: 'Use allowlist of permitted redirect destinations. Avoid using user input for redirect URLs. If redirects are required, use indirect references or validate against known safe patterns.',
     },
     [VulnerabilityCode.REDIRECT_JS_NAVIGATION]: {
-        id: 51,
+        id: 455,
         code: VulnerabilityCode.REDIRECT_JS_NAVIGATION,
         title: 'Open Redirect - JavaScript Navigation',
         description: 'Client-side open redirect vulnerability through JavaScript navigation methods like window.location or location.href being set to user-controlled values, allowing attackers to redirect users to malicious sites through specially crafted URLs that bypass server-side validation.',
@@ -144,7 +144,7 @@ export const SSRF_VULNERABILITIES = {
     // HOST HEADER INJECTION
     // ========================================
     [VulnerabilityCode.HOST_CACHE_POISONING]: {
-        id: 52,
+        id: 456,
         code: VulnerabilityCode.HOST_CACHE_POISONING,
         title: 'Host Header Injection - Cache Poisoning',
         description: 'Host header injection vulnerability where manipulated Host headers are reflected in cached responses, allowing attackers to poison web caches and CDNs with malicious content that is then served to all users, potentially enabling widespread defacement or malware distribution.',
@@ -166,7 +166,7 @@ export const SSRF_VULNERABILITIES = {
         remediation: 'Configure web servers to reject requests with unexpected Host headers. Include Host header in cache keys. Use canonical URLs for all generated links.',
     },
     [VulnerabilityCode.HOST_PASSWORD_RESET]: {
-        id: 53,
+        id: 457,
         code: VulnerabilityCode.HOST_PASSWORD_RESET,
         title: 'Host Header Injection - Password Reset Poisoning',
         description: 'Critical host header injection vulnerability in password reset functionality where the injected Host header is used to generate password reset URLs, allowing attackers to receive password reset tokens when victims click the manipulated links in legitimate reset emails.',
@@ -188,7 +188,7 @@ export const SSRF_VULNERABILITIES = {
         remediation: 'Use hardcoded canonical domain for generated URLs. Never trust Host header for security-sensitive functionality. Validate Host header against configured allowed hosts.',
     },
     [VulnerabilityCode.SSRF_FILTER_BYPASS]: {
-        id: 54,
+        id: 458,
         code: VulnerabilityCode.SSRF_FILTER_BYPASS,
         title: 'Server-Side Request Forgery - Filter Bypass',
         description: 'SSRF vulnerability that bypasses security filters through encoding tricks (URL encoding, IPv6 representation, decimal IP notation), DNS rebinding, or using alternative representations of blocked addresses to reach internal resources despite URL validation controls.',
@@ -210,7 +210,7 @@ export const SSRF_VULNERABILITIES = {
         remediation: 'Implement defense-in-depth with multiple validation layers. Resolve DNS before validation. Use strict URL parsing libraries. Block all private IP ranges including encoded forms.',
     },
     [VulnerabilityCode.REDIRECT_META_REFRESH]: {
-        id: 55,
+        id: 459,
         code: VulnerabilityCode.REDIRECT_META_REFRESH,
         title: 'Open Redirect - Meta Refresh',
         description: 'Open redirect vulnerability through HTML meta refresh tags where user input controls the redirect target URL, enabling phishing attacks by sending victims to malicious sites after a brief delay on the legitimate domain, bypassing some security controls.',
@@ -232,7 +232,7 @@ export const SSRF_VULNERABILITIES = {
         remediation: 'Validate meta refresh URLs against allowlist. Avoid using user input in meta refresh tags. Prefer server-side redirects with proper validation over client-side meta refresh.',
     },
     [VulnerabilityCode.HOST_REDIRECT]: {
-        id: 56,
+        id: 460,
         code: VulnerabilityCode.HOST_REDIRECT,
         title: 'Host Header Injection - Open Redirect',
         description: 'Host header injection leading to open redirect where the application uses the Host header to generate redirect URLs, allowing attackers to redirect users to malicious domains by manipulating the Host header in their requests.',

package/dist/categories/xss.js

@@ -6,7 +6,7 @@
 import { VulnerabilityCode } from '../error-codes.js';
 export const XSS_VULNERABILITIES = {
     [VulnerabilityCode.XSS_REFLECTED]: {
-        id: 31,
+        id: 400,
         code: VulnerabilityCode.XSS_REFLECTED,
         title: 'Cross-Site Scripting - Reflected',
         description: 'Reflected XSS vulnerability where user input is immediately returned by the server in the response without proper encoding, allowing attackers to inject malicious scripts that execute in the victim browser when they click a crafted link or submit a manipulated form.',
@@ -28,7 +28,7 @@ export const XSS_VULNERABILITIES = {
         remediation: 'HTML-encode all user input before rendering in HTML. Implement Content Security Policy (CSP). Use context-aware output encoding based on output location (HTML, JS, CSS, URL).',
     },
     [VulnerabilityCode.XSS_STORED]: {
-        id: 32,
+        id: 401,
         code: VulnerabilityCode.XSS_STORED,
         title: 'Cross-Site Scripting - Stored',
         description: 'Critical stored XSS vulnerability where malicious scripts are permanently saved in the application database and served to all users who view the affected content, enabling widespread session hijacking, credential theft, and malware distribution without requiring victim interaction beyond normal usage.',
@@ -50,7 +50,7 @@ export const XSS_VULNERABILITIES = {
         remediation: 'Sanitize all user input before storage. HTML-encode all dynamic content in responses. Implement strict Content Security Policy. Use HTTP-only and Secure flags for session cookies.',
     },
     [VulnerabilityCode.XSS_DOM_BASED]: {
-        id: 33,
+        id: 402,
         code: VulnerabilityCode.XSS_DOM_BASED,
         title: 'Cross-Site Scripting - DOM Based',
         description: 'DOM-based XSS vulnerability where the attack payload is processed entirely in the client-side JavaScript code without being sent to the server, typically through dangerous sinks like innerHTML, document.write(), or eval() that process URL fragments or user-controlled DOM elements.',
@@ -72,7 +72,7 @@ export const XSS_VULNERABILITIES = {
         remediation: 'Avoid using dangerous DOM sinks like innerHTML and document.write(). Use textContent instead of innerHTML. Sanitize any DOM manipulation with user input. Implement Trusted Types if supported.',
     },
     [VulnerabilityCode.XSS_SVG_INJECTION]: {
-        id: 34,
+        id: 403,
         code: VulnerabilityCode.XSS_SVG_INJECTION,
         title: 'Cross-Site Scripting - SVG Injection',
         description: 'SVG-based XSS vulnerability where malicious JavaScript is embedded within SVG image files using script elements or event handlers like onload, which execute when the browser renders the SVG file as an image or inline element, bypassing image upload security controls.',
@@ -94,7 +94,7 @@ export const XSS_VULNERABILITIES = {
         remediation: 'Sanitize uploaded SVG files to remove script elements and event handlers. Serve user-uploaded SVGs from a separate domain. Set Content-Disposition: attachment for SVG downloads. Use Content-Security-Policy.',
     },
     [VulnerabilityCode.XSS_CSTI_ANGULAR]: {
-        id: 35,
+        id: 404,
         code: VulnerabilityCode.XSS_CSTI_ANGULAR,
         title: 'Cross-Site Scripting - Angular Template Injection',
         description: 'AngularJS client-side template injection vulnerability where user input containing Angular expressions like {{constructor.constructor("alert(1)")()}} is evaluated by the Angular template engine, leading to arbitrary JavaScript execution in the user browser context.',
@@ -117,7 +117,7 @@ export const XSS_VULNERABILITIES = {
         remediation: 'Upgrade from AngularJS to modern Angular which is not vulnerable to template injection. Use ng-non-bindable directive for user content. Encode special characters {{}} in user input. Apply strict CSP.',
     },
     [VulnerabilityCode.XSS_CSP_BYPASS]: {
-        id: 36,
+        id: 405,
         code: VulnerabilityCode.XSS_CSP_BYPASS,
         title: 'Cross-Site Scripting - CSP Bypass',
         description: 'XSS vulnerability that bypasses Content Security Policy protections through techniques like JSONP endpoints on whitelisted domains, base tag injection, Angular.js libraries on CDN, or other CSP bypass gadgets that allow script execution despite CSP controls being in place.',
@@ -139,7 +139,7 @@ export const XSS_VULNERABILITIES = {
         remediation: 'Review CSP for JSONP endpoints and Angular.js CDN inclusions. Use nonce-based CSP instead of allowlist domains. Add base-uri restriction. Fix the underlying XSS vulnerability.',
     },
     [VulnerabilityCode.XSS_JS_CONTEXT]: {
-        id: 37,
+        id: 406,
         code: VulnerabilityCode.XSS_JS_CONTEXT,
         title: 'Cross-Site Scripting - JavaScript Context',
         description: 'XSS vulnerability where user input is injected directly into JavaScript code blocks, allowing attackers to break out of string contexts and execute arbitrary JavaScript by injecting quote characters and script code, or modify application logic by injecting new statements.',
@@ -161,7 +161,7 @@ export const XSS_VULNERABILITIES = {
         remediation: 'Avoid inserting user data into JavaScript code. Use JSON.stringify() with proper encoding for data passed to JavaScript. Pass data through data attributes and access via DOM APIs instead.',
     },
     [VulnerabilityCode.XSS_EVENT_HANDLER]: {
-        id: 38,
+        id: 407,
         code: VulnerabilityCode.XSS_EVENT_HANDLER,
         title: 'Cross-Site Scripting - Event Handler Injection',
         description: 'XSS vulnerability through injection into HTML event handler attributes like onclick, onerror, onload, or onmouseover, allowing attackers to execute JavaScript when users interact with or simply view the affected page elements without requiring script tags.',
@@ -183,7 +183,7 @@ export const XSS_VULNERABILITIES = {
         remediation: 'Use proper HTML encoding for all user input in attributes. Avoid placing user input in event handler attributes. Use Content Security Policy with unsafe-inline disabled.',
     },
     [VulnerabilityCode.XSS_SCRIPT_INJECTION]: {
-        id: 39,
+        id: 408,
         code: VulnerabilityCode.XSS_SCRIPT_INJECTION,
         title: 'Cross-Site Scripting - Script Tag Injection',
         description: 'XSS vulnerability where attackers can inject complete script tags into the HTML response, enabling arbitrary JavaScript execution. This is often the most straightforward XSS exploitation when input is not properly sanitized before rendering.',
@@ -205,7 +205,7 @@ export const XSS_VULNERABILITIES = {
         remediation: 'Encode < and > characters in user input. Implement Content Security Policy. Use HTML sanitization libraries that remove script tags. Apply context-aware output encoding.',
     },
     [VulnerabilityCode.XSS_HTML_INJECTION]: {
-        id: 40,
+        id: 409,
         code: VulnerabilityCode.XSS_HTML_INJECTION,
         title: 'Cross-Site Scripting - HTML Injection',
         description: 'HTML injection vulnerability where attackers can inject arbitrary HTML elements that modify page structure, enabling phishing attacks through fake login forms, content spoofing, or combination with CSS to overlay malicious content over legitimate page elements.',
@@ -227,7 +227,7 @@ export const XSS_VULNERABILITIES = {
         remediation: 'HTML-encode all user input. Use allowlist-based HTML sanitization if rich text is required. Implement Content Security Policy to restrict form actions and frame sources.',
     },
     [VulnerabilityCode.XSS_ATTRIBUTE_INJECTION]: {
-        id: 41,
+        id: 410,
         code: VulnerabilityCode.XSS_ATTRIBUTE_INJECTION,
         title: 'Cross-Site Scripting - Attribute Injection',
         description: 'XSS vulnerability where user input is placed in HTML attributes without proper encoding, allowing attackers to break out of the attribute context and inject new attributes or event handlers by using quote characters and spaces.',
@@ -249,7 +249,7 @@ export const XSS_VULNERABILITIES = {
         remediation: 'HTML-encode quotes (single and double) when placing user input in attributes. Always use quoted attributes. Avoid placing user input in dangerous attributes like href, src, or event handlers.',
     },
     [VulnerabilityCode.XSS_CSS_INJECTION]: {
-        id: 42,
+        id: 411,
         code: VulnerabilityCode.XSS_CSS_INJECTION,
         title: 'Cross-Site Scripting - CSS Injection',
         description: 'CSS injection vulnerability where attackers can inject malicious CSS rules to exfiltrate data through CSS selectors and background URLs, modify page appearance for phishing, or in older browsers achieve JavaScript execution through CSS expressions.',
@@ -271,7 +271,7 @@ export const XSS_VULNERABILITIES = {
         remediation: 'Sanitize CSS input to remove url() functions and expression() directives. Use CSS-specific encoding. Implement Content Security Policy with style-src restrictions.',
     },
     [VulnerabilityCode.XSS_TEMPLATE_LITERAL]: {
-        id: 43,
+        id: 412,
         code: VulnerabilityCode.XSS_TEMPLATE_LITERAL,
         title: 'Cross-Site Scripting - Template Literal Injection',
         description: 'XSS vulnerability through JavaScript template literals (backtick strings) where user input can break out of the template context or inject expressions using ${} syntax, executing arbitrary JavaScript in the client browser context.',
@@ -293,7 +293,7 @@ export const XSS_VULNERABILITIES = {
         remediation: 'Avoid placing user input inside template literals. Escape backticks, dollar signs, and braces. Use tagged template functions with proper escaping for user data.',
     },
     [VulnerabilityCode.XSS_MUTATION_BASED]: {
-        id: 44,
+        id: 413,
         code: VulnerabilityCode.XSS_MUTATION_BASED,
         title: 'Cross-Site Scripting - Mutation XSS',
         description: 'Mutation-based XSS (mXSS) vulnerability exploiting browser HTML parser quirks and DOM mutations where seemingly safe HTML is transformed into executable script through browser parsing behaviors, bypassing traditional sanitization.',
@@ -315,7 +315,7 @@ export const XSS_VULNERABILITIES = {
         remediation: 'Use DOMPurify or similar mXSS-aware sanitizers. Avoid innerHTML with user content. Implement Trusted Types. Stay updated on browser parsing behavior changes.',
     },
     [VulnerabilityCode.XSS_CSTI_VUE]: {
-        id: 45,
+        id: 414,
         code: VulnerabilityCode.XSS_CSTI_VUE,
         title: 'Cross-Site Scripting - Vue.js Template Injection',
         description: 'Vue.js client-side template injection vulnerability where user input containing Vue expression syntax like {{}} or v-bind directives is evaluated by the Vue template compiler, leading to arbitrary JavaScript execution in the browser context.',

package/dist-cjs/categories/authentication.js

@@ -12,7 +12,7 @@ exports.AUTH_VULNERABILITIES = {
     // JWT VULNERABILITIES
     // ========================================
     [error_codes_js_1.VulnerabilityCode.JWT_NONE_ALGORITHM]: {
-        id: 57,
+        id: 100,
         code: error_codes_js_1.VulnerabilityCode.JWT_NONE_ALGORITHM,
         title: 'JWT Vulnerability - None Algorithm Attack',
         description: 'Critical JWT vulnerability where the server accepts tokens with "alg": "none" in the header, allowing attackers to forge valid tokens without knowing the secret key by simply removing the signature and modifying claims to impersonate any user including administrators.',
@@ -34,7 +34,7 @@ exports.AUTH_VULNERABILITIES = {
         remediation: 'Explicitly specify allowed algorithms during JWT verification and reject "none". Use libraries that do not support "none" algorithm. Always validate the algorithm header against expected values.',
     },
     [error_codes_js_1.VulnerabilityCode.JWT_WEAK_SECRET]: {
-        id: 58,
+        id: 101,
         code: error_codes_js_1.VulnerabilityCode.JWT_WEAK_SECRET,
         title: 'JWT Vulnerability - Weak Secret Key',
         description: 'JWT implementation using a weak or common secret key for HMAC signature verification that can be brute-forced or found in common secret dictionaries, allowing attackers to forge arbitrary valid tokens and bypass authentication to access any user account.',
@@ -56,7 +56,7 @@ exports.AUTH_VULNERABILITIES = {
         remediation: 'Use cryptographically strong random secrets of at least 256 bits. Consider using asymmetric algorithms (RS256, ES256) instead of HMAC. Rotate secrets periodically.',
     },
     [error_codes_js_1.VulnerabilityCode.JWT_KEY_CONFUSION]: {
-        id: 59,
+        id: 102,
         code: error_codes_js_1.VulnerabilityCode.JWT_KEY_CONFUSION,
         title: 'JWT Vulnerability - Algorithm Confusion Attack',
         description: 'JWT key confusion vulnerability where the server public key can be used as an HMAC secret by switching the algorithm from RS256 to HS256, allowing attackers to forge valid tokens using the publicly available key to generate valid HMAC signatures.',
@@ -81,7 +81,7 @@ exports.AUTH_VULNERABILITIES = {
     // BROKEN ACCESS CONTROL
     // ========================================
     [error_codes_js_1.VulnerabilityCode.BAC_ANONYMOUS_ACCESS]: {
-        id: 60,
+        id: 103,
         code: error_codes_js_1.VulnerabilityCode.BAC_ANONYMOUS_ACCESS,
         title: 'Broken Access Control - Anonymous Access',
         description: 'Critical broken access control vulnerability where authenticated endpoints can be accessed without any authentication by simply removing auth headers or cookies, exposing sensitive functionality and data to unauthenticated attackers without any credential requirement.',
@@ -103,7 +103,7 @@ exports.AUTH_VULNERABILITIES = {
         remediation: 'Enforce authentication checks on all protected endpoints. Implement deny-by-default access control. Verify authentication state server-side before processing any request.',
     },
     [error_codes_js_1.VulnerabilityCode.BAC_IDOR]: {
-        id: 61,
+        id: 104,
         code: error_codes_js_1.VulnerabilityCode.BAC_IDOR,
         title: 'Broken Access Control - Insecure Direct Object Reference',
         description: 'IDOR vulnerability where users can access or modify resources belonging to other users by manipulating predictable identifiers like sequential IDs in URLs or request parameters, without proper authorization checks verifying resource ownership.',
@@ -125,7 +125,7 @@ exports.AUTH_VULNERABILITIES = {
         remediation: 'Implement proper authorization checks verifying resource ownership. Use unpredictable identifiers (UUIDs). Apply consistent access control policies across all endpoints.',
     },
     [error_codes_js_1.VulnerabilityCode.BAC_VERTICAL_PRIVILEGE]: {
-        id: 62,
+        id: 105,
         code: error_codes_js_1.VulnerabilityCode.BAC_VERTICAL_PRIVILEGE,
         title: 'Broken Access Control - Vertical Privilege Escalation',
         description: 'Vertical privilege escalation vulnerability allowing regular users to access or perform administrative functions by directly accessing admin endpoints or manipulating role/permission parameters, bypassing role-based access controls to gain elevated privileges.',
@@ -150,7 +150,7 @@ exports.AUTH_VULNERABILITIES = {
     // MASS ASSIGNMENT
     // ========================================
     [error_codes_js_1.VulnerabilityCode.MASSASSIGN_ROLE_ESCALATION]: {
-        id: 63,
+        id: 106,
         code: error_codes_js_1.VulnerabilityCode.MASSASSIGN_ROLE_ESCALATION,
         title: 'Mass Assignment - Role Escalation',
         description: 'Mass assignment vulnerability allowing attackers to escalate privileges by including additional parameters like "role", "isAdmin", or "permissions" in requests that the application binds to user objects without proper allowlist filtering of settable fields.',
@@ -172,7 +172,7 @@ exports.AUTH_VULNERABILITIES = {
         remediation: 'Use allowlist of permitted fields for each endpoint. Implement separate DTOs for input binding. Never auto-bind request data to domain objects without explicit field selection.',
     },
     [error_codes_js_1.VulnerabilityCode.MASSASSIGN_PROTOTYPE_POLLUTION]: {
-        id: 64,
+        id: 107,
         code: error_codes_js_1.VulnerabilityCode.MASSASSIGN_PROTOTYPE_POLLUTION,
         title: 'Mass Assignment - Prototype Pollution',
         description: 'JavaScript prototype pollution vulnerability through mass assignment where attackers inject __proto__ or constructor.prototype properties that modify the Object prototype globally, potentially leading to denial of service, security bypass, or remote code execution.',
@@ -194,7 +194,7 @@ exports.AUTH_VULNERABILITIES = {
         remediation: 'Freeze Object.prototype. Use Object.create(null) for objects used as maps. Filter __proto__ and constructor properties from user input. Use --frozen-intrinsics Node.js flag.',
     },
     [error_codes_js_1.VulnerabilityCode.JWT_EXPIRED_TOKEN]: {
-        id: 65,
+        id: 108,
         code: error_codes_js_1.VulnerabilityCode.JWT_EXPIRED_TOKEN,
         title: 'JWT Vulnerability - Expired Token Accepted',
         description: 'JWT implementation does not properly validate token expiration (exp claim), accepting expired tokens that should be rejected. This allows attackers with previously captured tokens to reuse them indefinitely, maintaining unauthorized access without credential updates.',
@@ -216,7 +216,7 @@ exports.AUTH_VULNERABILITIES = {
         remediation: 'Always validate exp claim during token verification. Set appropriate token lifetimes. Implement token refresh mechanisms. Use server-side session invalidation for immediate revocation.',
     },
     [error_codes_js_1.VulnerabilityCode.JWT_MISSING_CLAIMS]: {
-        id: 66,
+        id: 109,
         code: error_codes_js_1.VulnerabilityCode.JWT_MISSING_CLAIMS,
         title: 'JWT Vulnerability - Missing Required Claims',
         description: 'JWT tokens are missing critical security claims like exp (expiration), iat (issued at), nbf (not before), or iss (issuer), reducing the security guarantees of the token system and potentially allowing token reuse, replay attacks, or cross-tenant access.',
@@ -238,7 +238,7 @@ exports.AUTH_VULNERABILITIES = {
         remediation: 'Include and validate all standard claims: exp, iat, nbf, iss, aud, sub. Define required claims for your application. Reject tokens missing mandatory claims.',
     },
     [error_codes_js_1.VulnerabilityCode.BAC_HORIZONTAL_PRIVILEGE]: {
-        id: 67,
+        id: 110,
         code: error_codes_js_1.VulnerabilityCode.BAC_HORIZONTAL_PRIVILEGE,
         title: 'Broken Access Control - Horizontal Privilege Escalation',
         description: 'Horizontal privilege escalation vulnerability where authenticated users can access data or perform actions belonging to other users at the same privilege level by manipulating user identifiers, object references, or session parameters without ownership verification.',
@@ -260,7 +260,7 @@ exports.AUTH_VULNERABILITIES = {
         remediation: 'Implement record-level authorization checks. Verify resource ownership against the authenticated user session. Use indirect references that map to actual resources server-side.',
     },
     [error_codes_js_1.VulnerabilityCode.MASSASSIGN_HIDDEN_FIELD]: {
-        id: 68,
+        id: 111,
         code: error_codes_js_1.VulnerabilityCode.MASSASSIGN_HIDDEN_FIELD,
         title: 'Mass Assignment - Hidden Field Manipulation',
         description: 'Mass assignment vulnerability where attackers can modify hidden form fields or server-side computed values like price, discount, userId, or timestamp by including them in request bodies, bypassing UI restrictions to manipulate business logic or data integrity.',
@@ -282,7 +282,7 @@ exports.AUTH_VULNERABILITIES = {
         remediation: 'Never trust client-provided values for server-computed fields. Use explicit DTOs with allowlisted fields. Recompute amounts, timestamps, and IDs server-side.',
     },
     [error_codes_js_1.VulnerabilityCode.JWT_CLAIM_TAMPERING]: {
-        id: 131,
+        id: 112,
         code: error_codes_js_1.VulnerabilityCode.JWT_CLAIM_TAMPERING,
         title: 'JWT - Claim Tampering',
         description: 'JWT claim tampering vulnerability where attackers can modify token claims such as roles, user IDs, or permissions and the server accepts the tampered token, enabling privilege escalation or unauthorized access.',
@@ -304,7 +304,7 @@ exports.AUTH_VULNERABILITIES = {
         remediation: 'Validate JWT signatures using strong algorithms and trusted keys. Reject unsigned or weakly signed tokens. Enforce claim validation and server-side authorization checks.',
     },
     [error_codes_js_1.VulnerabilityCode.JWT_KID_INJECTION]: {
-        id: 132,
+        id: 113,
         code: error_codes_js_1.VulnerabilityCode.JWT_KID_INJECTION,
         title: 'JWT - KID Header Injection',
         description: 'JWT key identifier (kid) injection vulnerability where attackers manipulate the kid header to influence key selection or file paths, potentially bypassing signature verification or loading attacker-controlled keys.',
@@ -326,7 +326,7 @@ exports.AUTH_VULNERABILITIES = {
         remediation: 'Avoid direct use of kid as a file path or URL. Use a strict allowlist of key IDs and map to known keys in configuration. Reject unexpected or oversized kid values.',
     },
     [error_codes_js_1.VulnerabilityCode.JWT_JKU_INJECTION]: {
-        id: 133,
+        id: 114,
         code: error_codes_js_1.VulnerabilityCode.JWT_JKU_INJECTION,
         title: 'JWT - JKU Header Injection',
         description: 'JWT JKU (JWK Set URL) header injection vulnerability where attackers can control the URL used to fetch signing keys, allowing them to supply their own keys and forge valid tokens.',
@@ -348,7 +348,7 @@ exports.AUTH_VULNERABILITIES = {
         remediation: 'Ignore untrusted JKU values or restrict to a strict allowlist of trusted JWKS endpoints. Pin keys or use local key material where possible.',
     },
     [error_codes_js_1.VulnerabilityCode.JWT_EMBEDDED_JWK]: {
-        id: 134,
+        id: 115,
         code: error_codes_js_1.VulnerabilityCode.JWT_EMBEDDED_JWK,
         title: 'JWT - Embedded JWK Injection',
         description: 'JWT embedded JWK vulnerability where attackers include their own JWK in the token header and the server accepts it as a trusted signing key, enabling forged tokens and authentication bypass.',
@@ -370,7 +370,7 @@ exports.AUTH_VULNERABILITIES = {
         remediation: 'Reject embedded JWKs from tokens unless explicitly required and validated against a trusted key set. Use pinned keys and strict header validation.',
     },
     [error_codes_js_1.VulnerabilityCode.JWT_X5C_INJECTION]: {
-        id: 135,
+        id: 116,
         code: error_codes_js_1.VulnerabilityCode.JWT_X5C_INJECTION,
         title: 'JWT - X5C Header Injection',
         description: 'JWT x5c header injection vulnerability where attackers provide an untrusted certificate chain, allowing them to influence key selection or bypass signature validation if certificate trust is not strictly enforced.',