Account takeover via unrotated session identifiers
Published Aug 4, 2025 · Updated Aug 18, 2025
Session fixation in givanz Vvveb 1.0.6.1 allows attackers to hijack authenticated user or administrator sessions via a fixed cookie. The user and administrator login methods retain a client-supplied PHPSESSID after authentication instead of generating a new session identifier. Exploitation requires planting the chosen cookie before a victim logs in; reuse then grants the victim's account privileges.
Summary
What happened
Session fixation in givanz Vvveb 1.0.6.1 allows attackers to hijack authenticated user or administrator sessions via a fixed cookie. The user and administrator login methods retain a client-supplied PHPSESSID after authentication instead of generating a new session identifier. Exploitation requires planting the chosen cookie before a victim logs in; reuse then grants the victim's account privileges.
The record
- CVE
- CVE-2025-8517
- Published
- Aug 4, 2025
- Updated
- Aug 18, 2025
- Vendor
- givanz
- Product
- Vvveb
- Classifications
- CWE-384, T1539
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 4, 2025CVE publishedPublication date reported by the CVE source.
- Aug 18, 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=1.0.6.1
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- Session Fixation in Vvveb CMS 1.0.6.1 proof of conceptproof of concept · demonstrated
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