CVE-2026-7635 json
coreActivity: Activity Logging for WordPress <= 3.0 - Unauthenticated PHP Object Injection via 'user_agent' Log Meta Field
published 2026-05-13 5 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-29901
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
The coreActivity: Activity Logging for WordPress plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.0. This is due to the plugin failing to validate or strip PHP serialization syntax from the User-Agent HTTP header before storing it in the logmeta table, and subsequently calling `maybe_unserialize()` on every retrieved `meta_value` in `query_metas()` without verifying the data was originally serialized by the application. This makes it possible for unauthenticated attackers to inject a crafted PHP serialized payload via the User-Agent header during any logged event (such as a failed login attempt), which, when an administrator views the Logs page, is deserialized and passed to `DeviceDetector::setUserAgent()`, triggering a Fatal TypeError that creates a persistent Denial of Service condition blocking administrator access to the Logs page entirely.
Patch / fix
- github.com/dev4press/coreactivity#3 pull request
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 5 mo ago
Exploit prediction
0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- gdragon coreActivity: Activity Logging for WordPress
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
- Technology feeds
References
- github.com /dev4press/coreactivity/pull/3/changes/1f09331d66de7cf4bba9b6e396b0d4e7597fcde2
- wordfence.com /threat-intel/vulnerabilities/id/59f30135-6dd9-4367-90a9-a10ad491357d?source=cve
- plugins.trac.wordpress.org /browser/coreactivity/trunk/vendor/dev4press/library/dev4press/wordpress/admin/Table.php#L290
- plugins.trac.wordpress.org /browser/coreactivity/tags/3.0/vendor/dev4press/library/dev4press/wordpress/admin/Table.php#L290
- plugins.trac.wordpress.org /browser/coreactivity/trunk/core/log/Core.php#L252
- plugins.trac.wordpress.org /browser/coreactivity/tags/3.0/core/log/Core.php#L252
- plugins.trac.wordpress.org /browser/coreactivity/trunk/vendor/dev4press/library/dev4press/core/plugins/DBLite.php#L268
- plugins.trac.wordpress.org /browser/coreactivity/tags/3.0/vendor/dev4press/library/dev4press/core/plugins/DBLite.php#L268
- plugins.trac.wordpress.org /browser/coreactivity/trunk/core/table/Logs.php#L161
- plugins.trac.wordpress.org /browser/coreactivity/tags/3.0/core/table/Logs.php#L161
- plugins.trac.wordpress.org /browser/coreactivity/trunk/core/log/Device.php#L35
- plugins.trac.wordpress.org /browser/coreactivity/tags/3.0/core/log/Device.php#L35
Sources
- CVE List CVE-2026-7635
- NVD CVE-2026-7635
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.