TOKUHIROM HTTP::Session2 up to 1.09 on Perl ID input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in TOKUHIROM HTTP::Session2 up to 1.09 on Perl. This issue affects some unknown processing. The manipulation of the argument ID leads to input validation. This vulnerability is traded as CVE-2018-25160. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in TOKUHIROM HTTP::Session2 up to 1.09 on Perl. It has been rated as critical. This issue affects an unknown functionality. The manipulation of the argument id with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
HTTP::Session2 versions through 1.09 for Perl does not validate the format of user provided session ids, enabling code injection or other impact depending on session backend. For example, if an application uses memcached for session storage, then it may be possible for a remote attacker to inject memcached commands in the session id value.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2018-25160 since 02/26/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/19/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2018-21615). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔒
ADP CISA Base Score: 6.5
ADP CISA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
02/26/2026 CVE reserved02/27/2026 Advisory disclosed
02/27/2026 VulDB entry created
03/19/2026 VulDB entry last update
Sources
Advisory: 813838f6d08034b6a265a70e53b59b941b5d3e6dStatus: Confirmed
CVE: CVE-2018-25160 (🔒)
GCVE (CVE): GCVE-0-2018-25160
GCVE (VulDB): GCVE-100-348209
EUVD: 🔒
Entry
Created: 02/27/2026 22:17Updated: 03/19/2026 13:49
Changes: 02/27/2026 22:17 (54), 02/28/2026 00:08 (1), 03/03/2026 22:23 (11), 03/19/2026 13:49 (10)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.