Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-7635 high CVSS 8.1

Unsafe Deserialization in coreActivity: Activity Logging for (WordPress plugin) (CVE-2026-7635)

Summary

Vulnerability in coreActivity: Activity Logging for (WordPress plugin) (CVE-2026-7635). Successful exploitation can lead to full system takeover. Exploitable via User-Agent header.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-7635 has been found in coreActivity: Activity Logging for (WordPress plugin).
Attackers can target a specific entry point like User-Agent header over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "coreActivity: Activity Logging for (WordPress plugin) CVE-2026-7635" on the vendor's site.

CVE-2026-7635 (coreActivity: Activity Logging for (WordPress plugin)) — CWE-502 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: User-Agent header / meta_value
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Unsafe deserialization (CWE-502) exists in coreActivity: Activity Logging for (WordPress plugin). Attackers reach the vulnerable code path via User-Agent header without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of coreActivity: Activity Logging for (WordPress plugin). Attack surface: User-Agent header / meta_value.

🔥 Severity

Severity: High (CVSS 8.1/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで coreActivity: Activity Logging for (WordPress plugin) を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details