Unauthenticated object injection via untrusted deserialization
Published Jul 16, 2025 · Updated Apr 28, 2026
PHP object injection in Guru Team Site Chat on Telegram 1.0.4 and earlier allows remote attackers to inject objects via untrusted input. Published sources do not identify the input field or function that passes attacker-controlled serialized data into PHP deserialization. Exploitation is unauthenticated, but damaging effects require a suitable POP chain from another installed plugin or theme; the resulting action depends on that chain.
Summary
What happened
PHP object injection in Guru Team Site Chat on Telegram 1.0.4 and earlier allows remote attackers to inject objects via untrusted input. Published sources do not identify the input field or function that passes attacker-controlled serialized data into PHP deserialization. Exploitation is unauthenticated, but damaging effects require a suitable POP chain from another installed plugin or theme; the resulting action depends on that chain.
The record
- CVE
- CVE-2025-30949
- Published
- Jul 16, 2025
- Updated
- Apr 28, 2026
- Vendor
- Guru Team
- Product
- Site Chat on Telegram
- Classifications
- CWE-502, CAPEC-586, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 16, 2025CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record 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 <=1.0.4 changes=[{"at":"1.0.6","status":"unaffected"}]
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
No public exploit references are available in this record.
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