CVE-2025-34452: Streama Subtitle Download Path Traversal and SSRF Leading to Arbitrary File Write
Streama versions 1.10.0 through 1.10.5 and prior to commit b7c8767 contain a combination of path traversal and server-side request forgery (SSRF) vulnerabilities in that allow an authenticated attacker to write arbitrary files to the server filesystem. The issue exists in the subtitle download functionality, where user-controlled parameters are used to fetch remote content and construct file paths without proper validation. By supplying a crafted subtitle download URL and a path traversal sequence in the file name, an attacker can write files to arbitrary locations on the server, potentially leading to remote code execution.
Security readout for executives and security teams
Plain-English summary
An authenticated Streama user could abuse subtitle downloading to make the server fetch attacker-controlled content and save it outside the intended subtitle directory. That can overwrite or create files on the server, creating a credible path to server compromise depending on deployment permissions.
Executive priority
Prioritize remediation for any production or internet-accessible Streama instance. The issue requires authentication, but the impact can reach arbitrary file write and possible remote code execution, which makes delay risky.
Technical view
The vulnerability combines SSRF and path traversal in Streama subtitle download handling. User-controlled URL and filename/path data are not sufficiently validated, allowing remote content retrieval and arbitrary filesystem writes. Sources identify Streama 1.10.0 through 1.10.5, before commit b7c8767, as affected.
Likely exposure
Exposure is limited to organizations running affected Streama versions with authenticated users who can access subtitle download functionality. Internet-facing Streama deployments or shared-user media environments have higher practical risk.
Exploitation context
The bundle cites a public technical write-up tagged as exploit, but KEV is false and no provided source states active exploitation in the wild. Treat exploit knowledge as public, not confirmed active abuse.
Researcher notes
Focus validation on the subtitle download data flow: remote fetch handling, filename canonicalization, output path construction, and write permissions. Avoid assuming RCE in every deployment; it depends on where the process can write and how written files are later used.
Mitigation direction
Apply Streama commit b7c8767 or a vendor release containing that fix.
Confirm whether any maintained vendor guidance supersedes the referenced commit.
Restrict Streama access to trusted users until remediation is complete.
Review filesystem permissions so the Streama process cannot write sensitive paths.
Monitor subtitle download activity and unexpected outbound requests.
Validation and detection
Inventory all Streama instances and record version or deployed commit.
Check whether each instance includes commit b7c8767 or later relevant fixes.
Verify subtitle download access is limited to intended authenticated users.
Review server filesystems for unexpected files near application or startup paths.
Review logs for suspicious subtitle download URLs or unusual file writes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.