dbcve.org
SimApplication

CVE-2025-15099

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-26
Fix available
A fix is available. Upgrade to after 0.5.27 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 vulnerability was identified in simstudioai sim up to 0.5.27. This vulnerability affects unknown code of the file apps/sim/lib/auth/internal.ts of the component CRON Secret Handler. The manipulation of the argument INTERNAL_API_SECRET leads to improper authentication. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. The identifier of the patch is e359dc2946b12ed5e45a0ec9c95ecf91bd18502a. Applying a patch is the recommended action to fix this issue.

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 · high confidence

A critical authentication bypass vulnerability exists in simstudioai sim up to 0.5.27 within the CRON secret handler in apps/sim/lib/auth/internal.ts. Attackers can manipulate the INTERNAL_API_SECRET argument to bypass authentication controls, allowing unauthorized access to protected functions. The exploit is publicly available and can be initiated remotely.

MitigationApply the provided patch (commit e359dc2946b12ed5e45a0ec9c95ecf91bd18502a) to fix the improper authentication in the CRON secret handler. As an immediate workaround, ensure INTERNAL_API_SECRET is not exposed or guessable and restrict network access to the CRON endpoint.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SimApplication
Affected:<= 0.5.27

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
High
Integrity
High
Availability
High

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

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 sim version
    Run 'sim --version' or check package.json for the simstudioai/sim package version
    Affected if Version is 0.5.27 or lower
  2. Locate the internal.ts auth file
    Find the file at apps/sim/lib/auth/internal.ts in the sim installation directory or source code repository
    Affected if File exists and contains the INTERNAL_API_SECRET definition
  3. Inspect for hardcoded secret value
    Open internal.ts and search for 'INTERNAL_API_SECRET' - examine the value assigned to it
    Affected if A hardcoded string literal is assigned (rather than being read from an environment variable or secrets manager)
  4. Verify secret source
    Check if the secret value is obtained from process.env, a secrets manager, or similar dynamic source
    Affected if The secret is hardcoded as a static string rather than fetched from environment or secrets management

You are affected if running sim version 0.5.27 or lower AND the INTERNAL_API_SECRET in apps/sim/lib/auth/internal.ts contains a hardcoded static value instead of being retrieved from environment variables or a secrets manager.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 0.5.27
Vendor patch github.com →
Interim mitigation

Apply the provided patch (commit e359dc2946b12ed5e45a0ec9c95ecf91bd18502a) to fix the improper authentication in the CRON secret handler. As an immediate workaround, ensure INTERNAL_API_SECRET is not exposed or guessable and restrict network access to the CRON endpoint.

Recommended fix High confidence

Any version > 0.5.27 containing the security fix (check release notes for when patch was integrated)

  1. 1. Review the vendor patch commit at https://github.com/simstudioai/sim/commit/e359dc2946b12ed5e45a0ec9c95ecf91bd18502a to understand the code changes
  2. 2. Navigate to the affected file: apps/sim/lib/auth/internal.ts in your local repository
  3. 3. Apply the authentication fix from the vendor patch - this likely involves proper validation of the INTERNAL_API_SECRET argument in the CRON Secret Handler
  4. 4. Verify the fix ensures proper authentication checks are performed before allowing access
  5. 5. Rebuild and redeploy the application
  6. 6. Ensure INTERNAL_API_SECRET is properly configured in production environment variables

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sim Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15099 — 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-2025-15099 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