Authenticated server-originated requests via restore filename
Published Aug 24, 2025 · Updated Aug 25, 2025
Server-side request forgery in wblog 0.0.1 allows remote authenticated users to make server-originated requests through fileName. RestorePost in controllers/backup.go treats attacker-controlled fileName as a requestable resource, causing requests to attacker-selected destinations. Successful exploitation lets an authenticated user reach resources available to the server, while published evidence reports a proof of concept rather than active exploitation.
Summary
What happened
Server-side request forgery in wblog 0.0.1 allows remote authenticated users to make server-originated requests through fileName. RestorePost in controllers/backup.go treats attacker-controlled fileName as a requestable resource, causing requests to attacker-selected destinations. Successful exploitation lets an authenticated user reach resources available to the server, while published evidence reports a proof of concept rather than active exploitation.
The record
- CVE
- CVE-2025-9395
- Published
- Aug 24, 2025
- Updated
- Aug 25, 2025
- Vendor
- wangsongyan
- Product
- wblog
- Classifications
- CWE-918, CAPEC-664, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 24, 2025CVE publishedPublication date reported by the CVE source.
- Aug 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- wblog RestorePost SSRF proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo