Quick answers
- Is CVE-2023-3360 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2023-3360 being exploited in the wild.
- How severe is CVE-2023-3360?
- Low severity, with a CVSS score of 3.3, published 2 September 2026.
- Which products and versions are affected?
- Weaver Show Posts before 1.8.1.
- Is there a fix for CVE-2023-3360?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2023-3360 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2023-3360?
- Check whether you run Weaver Show Posts at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a PHP object injection (CWE-502) in the file import functionality of Weaver Show Posts. When a user uploads a filter configuration file via the plugin's admin interface, the plugin passes the file content directly to PHP's unserialize() function without validation. An attacker with admin privileges can craft a serialized PHP object that exploits a gadget chain present in WordPress or installed plugins to execute arbitrary code. The attack requires high privilege (admin) user access and depends on the presence of a suitable gadget chain on the target blog. No patch availability information is explicitly stated in the advisory.
Affected products
- Weaver Show Posts before 1.8.1
Timeline
- 2023-09-02: disclosed