dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-15557

HIGH · 7.3 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A weakness has been identified in waooAI waoowaoo up to 0.4.1. Affected by this vulnerability is the function getInternalTaskSession/getAuthSession/requireUserAuth/requireProjectAuth/requireProjectAuthLight in the library src/lib/api-auth.ts of the component Internal Task Header Handler. This manipulation of the argument x-internal-user-id request causes improper authentication. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Improper authentication vulnerability in waooAI waoowaoo up to 0.4.1 where manipulation of the x-internal-user-id HTTP request header allows bypassing authentication checks in multiple authentication functions (getInternalTaskSession, getAuthSession, requireUserAuth, requireProjectAuth, requireProjectAuthLight) within src/lib/api-auth.ts. This appears to be a direct header injection/override issue where internal user identification can be controlled by attackers.

MitigationImplement proper validation and server-side verification of the x-internal-user-id header - the application should not trust client-supplied user identifiers for authentication decisions. Consider using server-generated session tokens or signed/encrypted user identifiers instead of direct header values.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed waooAI version
    Examine package.json, package-lock.json, or run 'npm list waoowaoo' or 'pip show waoowaoo' depending on the package manager used
    Affected if version is 0.4.1 or lower (any version up to and including 0.4.1)
  2. Identify if x-internal-user-id header is used
    Search source code for 'x-internal-user-id' string usage, particularly in src/lib/api-auth.ts or similar authentication modules
    Affected if the header is referenced in authentication-related code without server-side validation
  3. Inspect authentication function implementations
    Examine the affected functions (getInternalTaskSession, getAuthSession, requireUserAuth, requireProjectAuth, requireProjectAuthLight) in src/lib/api-auth.ts to see if they directly use the x-internal-user-id header value
    Affected if these functions accept the header value as trusted user identity without cryptographic verification or server-side lookup
  4. Check for server-side validation of the header
    Search for validation logic that verifies the x-internal-user-id header against a trusted source (database lookup, token verification, signed session) before using it for auth decisions
    Affected if no validation exists - the header is used directly in authentication checks
  5. Test header manipulation in authentication endpoints
    Send authenticated API requests while modifying or adding the x-internal-user-id header to an arbitrary value and observe if authentication state changes
    Affected if supplying a different user ID in the header alters the authenticated user context

You are affected if waooAI waoowaoo version is 0.4.1 or lower AND your application uses the x-internal-user-id header in authentication without validating it server-side.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper validation and server-side verification of the x-internal-user-id header - the application should not trust client-supplied user identifiers for authentication decisions. Consider using server-generated session tokens or signed/encrypted user identifiers instead of direct header values.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15557 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15557 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data