Contributor-level object injection via untrusted deserialization
Published Nov 6, 2025 · Updated Nov 6, 2025
PHP object injection in Preserve Code Formatting 4.0.1 and earlier allows remote authenticated users to instantiate arbitrary PHP objects. Patchstack and the upstream changelog identify untrusted deserialization and object injection, but neither publishes the affected function, input, or data flow. Contributor-level access is required, and further impact depends on a usable property-oriented programming chain in the WordPress installation.
Summary
What happened
PHP object injection in Preserve Code Formatting 4.0.1 and earlier allows remote authenticated users to instantiate arbitrary PHP objects. Patchstack and the upstream changelog identify untrusted deserialization and object injection, but neither publishes the affected function, input, or data flow. Contributor-level access is required, and further impact depends on a usable property-oriented programming chain in the WordPress installation.
The record
- CVE
- CVE-2025-49386
- Published
- Nov 6, 2025
- Updated
- Nov 6, 2025
- Vendor
- Scott Reilly
- Product
- Preserve Code Formatting
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 6, 2025CVE publishedPublication date reported by the CVE source.
- Nov 6, 2025Record 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=n/a <=<= 4.0.1 changes=[{"at":"5.0","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