Unauthenticated PHP object injection
Published Jun 17, 2025 · Updated Apr 28, 2026
PHP object injection in yuliaz Rapyd Payment Extension for WooCommerce 1.2.0 and earlier allows remote attackers to inject PHP objects. Public sources do not identify the affected function, input parameter, or code path that deserializes attacker-controlled data. Exploitation requires no account, but file deletion, data disclosure, or code execution additionally requires a usable POP chain supplied by another installed plugin or theme.
Summary
What happened
PHP object injection in yuliaz Rapyd Payment Extension for WooCommerce 1.2.0 and earlier allows remote attackers to inject PHP objects. Public sources do not identify the affected function, input parameter, or code path that deserializes attacker-controlled data. Exploitation requires no account, but file deletion, data disclosure, or code execution additionally requires a usable POP chain supplied by another installed plugin or theme.
The record
- CVE
- CVE-2025-30618
- Published
- Jun 17, 2025
- Updated
- Apr 28, 2026
- Vendor
- yuliaz
- Product
- Rapyd Payment Extension for WooCommerce
- Classifications
- CWE-502, CAPEC-586, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 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.2.0 changes=[{"at":"1.2.1","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