Blog

"Prevention is cheaper than a breach"

Home / Threats / CVE-2026-7635

CVE-2026-7635 - Activity Logging For Wordpress Plugin

CVE-2026-7635

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.

CVE-2026-7635

HIGH CVSS 8.1 Published 2026-05-13 Updated 2026-05-13
AI Risk Critical (99/100) Active Exploit: Likely Published Exploit: Public exploit references found Priority: P1 Immediate
Severity Band HIGH
CVSS Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected Components 3
Reference Links 10
AI Risk Engine Critical (99/100)
Exploitability High
Active Exploitation Likely
Published Exploit Status Public exploit references found

Threat Timeline

  1. 2026-05-13 CVE published and first recorded in the threat feed.
  2. 2026-05-13 Record updated with latest vulnerability metadata.
  3. 2026-05-24 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 8 days ago

AI enriched 8 days ago (2026-05-24 00:18 UTC)

Technical 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…

Potential Impact

Severity is HIGH (CVSS 8.1). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on published exploit references, low-bar exploit prerequisites.

Primary risk drivers: published exploit references, low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 99/100 (Critical, High) with priority P1 Immediate. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

References

Scroll to top