Authenticated object injection via unsafe deserialization
Published Apr 1, 2025 · Updated Apr 28, 2026
PHP object injection in MagePeople Team WpTravelly 1.8.7 and earlier allows remote authenticated users to inject objects through untrusted input. The public record identifies unsafe deserialization as the operation but does not disclose the affected parameter, endpoint, file, or function. Contributor-level access is required, and further impact depends on a suitable PHP property-oriented programming chain.
Summary
What happened
PHP object injection in MagePeople Team WpTravelly 1.8.7 and earlier allows remote authenticated users to inject objects through untrusted input. The public record identifies unsafe deserialization as the operation but does not disclose the affected parameter, endpoint, file, or function. Contributor-level access is required, and further impact depends on a suitable PHP property-oriented programming chain.
The record
- CVE
- CVE-2025-30892
- Published
- Apr 1, 2025
- Updated
- Apr 28, 2026
- Vendor
- MagePeople Team
- Product
- WpTravelly
- Classifications
- CWE-502, CAPEC-586, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 1, 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.8.7 changes=[{"at":"1.8.8","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