dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-34300

CRITICAL · 10.0 CVSS v4.0 Published 2025-07-16
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
High EPSS Remotely reachable No privileges Zero-click

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 template injection vulnerability exists in Sawtooth Software’s Lighthouse Studio versions prior to 9.16.14 via the  ciwweb.pl http://ciwweb.pl/  Perl web application. Exploitation allows an unauthenticated attacker can execute arbitrary commands.

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

Template injection vulnerability in Sawtooth Lighthouse Studio's ciwweb.pl Perl web application allows unauthenticated attackers to execute arbitrary commands on the underlying system. The vulnerability exists in versions prior to 9.16.14.

MitigationUpgrade to Lighthouse Studio version 9.16.14 or later to remediate this vulnerability. If immediate upgrade is not feasible, consider network segmentation or disabling the affected ciwweb.pl component until patching can be completed.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify if Lighthouse Studio is installed
    Check for the presence of Sawtooth Lighthouse Studio on the system. Look for installation directories, or search for the ciwweb.pl file typically located in the web server's CGI-bin or web application directory.
    Affected if Lighthouse Studio or the ciwweb.pl component is found on the system
  2. Locate the ciwweb.pl version
    Open the ciwweb.pl file in a text editor and look for version strings within the Perl code, or check the application banner if exposed via HTTP HEAD/GET requests to the web endpoint.
    Affected if The ciwweb.pl file version is displayed or embedded in the application
  3. Determine the Lighthouse Studio version
    Check the Lighthouse Studio application version through its installed metadata, readme files, or the software's about/help section if accessible.
    Affected if A version number lower than 9.16.14 is reported for the Lighthouse Studio installation
  4. Verify ciwweb.pl is web-accessible
    Confirm the ciwweb.pl script is accessible via the web server by accessing its URL endpoint (e.g., http://yourserver/cgi-bin/ciwweb.pl). The vulnerability is exploitable only when the web interface is exposed.
    Affected if The ciwweb.pl web endpoint responds to HTTP requests and is reachable from a network perspective
  5. Compare version to affected range
    If a version number is identified, compare it against the affected range: versions prior to 9.16.14 are vulnerable. Any version below 9.16.14 is within the affected range.
    Affected if The installed version is below 9.16.14 (e.g., 9.16.13, 9.15.x, or earlier)

The environment is affected if Sawtooth Lighthouse Studio with ciwweb.pl is installed, the version is below 9.16.14, and the web interface is accessible.

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

Upgrade to Lighthouse Studio version 9.16.14 or later to remediate this vulnerability. If immediate upgrade is not feasible, consider network segmentation or disabling the affected ciwweb.pl component until patching can be completed.

Recommended fix Moderate confidence

Lighthouse Studio version 9.16.14

  1. 1. Identify the currently installed version of Sawtooth Lighthouse Studio by checking the application or its configuration files
  2. 2. If the installed version is prior to 9.16.14, download version 9.16.14 or later from the official Sawtooth Software vendor
  3. 3. Follow the vendor's documented upgrade procedure to apply the update
  4. 4. After upgrading, verify the ciwweb.pl application is functioning correctly
  5. 5. Confirm the version has been updated to 9.16.14 or later

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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