GHSA-H29G-C9CX-C73Q
Vulnerability from github – Published: 2026-05-11 17:53 – Updated: 2026-05-11 17:53Summary
Hi, there. We've found PHP Serialize Injections in your project “torrentpier". According to the OWASP, it can pose a significant risk: enable an attacker to modify serialized objects in order to inject malicious data into the application code, resulting in code execution or an arbitrary reading of the file on any vulnerable system.
Details
In the attachment you can find a report with the number of vulnerabilities, their types and the vulnerable files. To view the lines of vulnerable code you may scan your project with the "PHP Secure" vulnerability scanner with a full access to it.
PoC

About Us
We are a team of developers of the PHP Secure vulnerability scanner. First, we checked your code automatically. Then we reviewed the vulnerable code more deeply manually and felt it was necessary to report about it to you. We suggest you scanning your code and address vulnerabilities as soon as possible to prevent a potential breach.
If you have any questions, email us at support@phpsecure.net"
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 2.4.3"
},
"package": {
"ecosystem": "Packagist",
"name": "torrentpier/torrentpier"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.4.4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-502"
],
"github_reviewed": true,
"github_reviewed_at": "2026-05-11T17:53:20Z",
"nvd_published_at": null,
"severity": "CRITICAL"
},
"details": "### Summary\nHi, there. We\u0027ve found PHP Serialize Injections in your project \u201ctorrentpier\". According to the OWASP, it can pose a significant risk: enable an attacker to modify serialized objects in order to inject malicious data into the application code, resulting in code execution or an arbitrary reading of the file on any vulnerable system. \n \n### Details\nIn the attachment you can find a report with the number of vulnerabilities, their types and the vulnerable files. To view the lines of vulnerable code you may scan your project with the \"[PHP Secure](https://phpsecure.net/?utm_source=github\u0026utm_term=torrentpier\u0026utm_content=torrentpier)\" vulnerability scanner with a full access to it.\n\n### PoC\n\u003cimg width=\"663\" alt=\"Screenshot 2023-09-25 at 11 12 32 AM\" src=\"https://user-images.githubusercontent.com/118765013/270273991-4a2c3884-3ab0-48ad-af77-3f3dbfa64e2a.png\"\u003e\n\u003cimg width=\"661\" alt=\"Screenshot 2023-09-25 at 11 12 43 AM\" src=\"https://user-images.githubusercontent.com/118765013/270274006-247ed9d3-2dc0-4a87-8f1f-89079c8be165.png\"\u003e\n\u003cimg width=\"664\" alt=\"Screenshot 2023-09-25 at 11 12 53 AM\" src=\"https://user-images.githubusercontent.com/118765013/270274018-b99d6ec2-4c5a-439f-b089-9e11345e963d.png\"\u003e\n\u003cimg width=\"662\" alt=\"Screenshot 2023-09-25 at 11 13 13 AM\" src=\"https://user-images.githubusercontent.com/118765013/270274023-36ecffc7-215d-41db-b3ba-6aa677e644d3.png\"\u003e\n\n### About Us\nWe are a team of developers of the PHP Secure vulnerability scanner. First, we checked your code automatically. Then we reviewed the vulnerable code more deeply manually and felt it was necessary to report about it to you. We suggest you scanning your code and address vulnerabilities as soon as possible to prevent a potential breach.\n\nIf you have any questions, email us at support@phpsecure.net\"",
"id": "GHSA-h29g-c9cx-c73q",
"modified": "2026-05-11T17:53:20Z",
"published": "2026-05-11T17:53:20Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/torrentpier/torrentpier/security/advisories/GHSA-h29g-c9cx-c73q"
},
{
"type": "PACKAGE",
"url": "https://github.com/torrentpier/torrentpier"
}
],
"schema_version": "1.4.0",
"severity": [],
"summary": "torrentpier has PHP Serialize Injections"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.