dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-58361

CRITICAL · 9.3 CVSS v3.1 Published 2025-09-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Promptcraft Forge Studio is a toolkit for evaluating, optimizing, and maintaining LLM-powered applications. All versions contain an non-exhaustive URL scheme check that does not protect against XSS. User-controlled URLs pass through src/utils/validation.ts, but the check only strips `javascript:` and a few patterns. `data:` URLs (for example data:image/svg+xml,…) still pass. If a sanitized value is used in href/src, an attacker can execute a script. There is currently no fix for 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

Promptcraft Forge Studio contains an incomplete URL scheme validation in src/utils/validation.ts that only strips javascript: and a few patterns while allowing data: URLs (e.g., data:image/svg+xml). When sanitized URLs are used in href or src attributes, attackers can inject malicious scripts via data: URLs containing SVG or HTML with embedded JavaScript.

MitigationImplement a comprehensive URL scheme allowlist that explicitly permits only http: and https: schemes while rejecting all others including data:, javascript:, vbscript:, and any other potentially dangerous schemes.

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

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

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. Locate the vulnerable validation file
    Search for the file src/utils/validation.ts in your Promptcraft Forge Studio installation directory and confirm it exists.
    Affected if The file exists and contains URL validation logic.
  2. Inspect the validation logic for incomplete scheme filtering
    Open src/utils/validation.ts and examine the URL validation function. Look for patterns that strip javascript: or vbscript: but do not explicitly reject data: URLs.
    Affected if The validation only checks for javascript: or similar schemes but fails to block data: URLs.
  3. Find usages of the validation function with href or src attributes
    Search your codebase for calls to the validation function and examine where its output is used. Specifically look for template or render code that assigns validated URLs to href, src, or similar HTML attributes.
    Affected if The sanitized output is assigned to href or src attributes in HTML elements.
  4. Determine if user-controlled input reaches the validation
    Trace the data flow from user inputs (request parameters, form fields, API payloads) to the validation function and then to href/src attributes. Identify whether external or user-supplied values can reach this path.
    Affected if User-provided or external data flows through the validation and into href/src attributes without additional sanitization.

You are affected if Promptcraft Forge Studio is deployed, src/utils/validation.ts contains incomplete URL scheme filtering that fails to block data: URLs, and user-controlled URLs are rendered in href or src attributes.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement a comprehensive URL scheme allowlist that explicitly permits only http: and https: schemes while rejecting all others including data:, javascript:, vbscript:, and any other potentially dangerous schemes.

Recommended fix High confidence
  1. Monitor the official Promptcraft Forge Studio repository (github.com) and security advisories for the availability of a fix
  2. Consider implementing additional input validation/sanitization at the application layer where the validated URLs are used
  3. Avoid using unvalidated user-controlled URLs in href or src attributes until a fix is released
  4. Implement Content Security Policy (CSP) headers to mitigate potential XSS impact

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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