Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege WordPress account
-
DeliverySubmit crafted serialized PHP payload
-
ExploitTrigger unsafe deserialization (object injection)
-
ExecutionGadget chain executes during object lifecycle
-
ImpactCompromise site data or execute code
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated attacker with at least low privileges (CVSS PR:L) on a WordPress site running GS Logo Slider up to and including 3.8.9; the attacker must reach a plugin input that is deserialized without validation and supply crafted serialized PHP data. Meaningful impact additionally depends on a usable POP gadget chain being available in the plugin, WordPress core, or another installed plugin/theme - a factor that limits exploitation in hardened or minimal installations. The specific vulnerable parameter/endpoint and the triggering mechanism are not described in the available sources. Limiting factors: valid low-privilege credentials are required (not unauthenticated), and exploitation is bounded by gadget-chain availability in the target environment. |
| Impact | This is a genuine prioritization candidate but short of an emergency. The supplied CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) describes a network-reachable, low-complexity flaw requiring only low privileges and no user interaction, with high confidentiality, integrity and availability impact - consistent with PHP Object Injection that can escalate to code execution or data compromise when a usable gadget chain is present. The vuln.today decision label is 'this_week', which indicates meaningful urgency without being 'act_now' or 'emergency'. Countervailing signals temper the raw score: there is no CISA KEV listing (not confirmed actively exploited), no EPSS score was provided in the input (exploitation probability unknown - do not assume high or low), and no verified public exploit code. The PR:L requirement is also a real gatekeeper - exploitation presupposes an attacker already holding at least a low-privilege authenticated account on the target WordPress site, which lowers real-world risk relative to a fully unauthenticated flaw. Net: credible high-severity issue warranting prompt patching per the 'this_week' label, but not evidenced as under active mass exploitation. |
| Exploit ScenarioDerived | An attacker holding a low-privilege authenticated account (per CVSS PR:L) on a WordPress site running GS Logo Slider ≤ 3.8.9 submits crafted serialized PHP data to an input that the plugin deserializes without validation. If a suitable property-oriented programming (POP) gadget chain exists in the plugin, WordPress core, or another installed component, the resulting object injection can lead to data tampering, information disclosure, or code execution. No public exploit was identified at the time of analysis, and the exact triggering parameter is not described in the available sources. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
GS Logo Slider, a WordPress plugin from GS Plugins, is affected through version 3.8.9 by PHP object injection: untrusted data reaching a deserialization routine lets an attacker with at least low-privilege access on a WordPress site instantiate arbitrary objects, with a CVSS score of 8.8 reflecting high confidentiality, integrity and availability impact. Because exploitation depends on a usable POP gadget chain being present in the plugin, WordPress core, or another installed plugin or theme, real-world risk varies by installation; the specific vulnerable parameter and trigger are not described in the available sources. A public PoC reference exists in the Patchstack advisory, but it is not verified as working exploit code, and there is no confirmed active exploitation (no CISA KEV listing).
RemediationAI
No vendor-released patch or fixed version is identified in the available data, so the primary action is to track the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/gs-logo-slider/vulnerability/wordpress-gs-logo-slider-plugin-3-8-9-php-object-injection-vulnerability?_s_id=cve) for an updated plugin release and apply it as soon as it appears. Until then, compensating controls center on the prerequisites stated for this issue: since exploitation requires at least low-privilege credentials (CVSS PR:L), review and tighten WordPress user roles so subscriber and other low-privilege accounts are granted only what they genuinely need, and remove stale or unused accounts - the trade-off is tighter operational overhead for site editors. Because impact further depends on a usable gadget chain in the plugin, WordPress core, or other installed plugins and themes, reducing the number of installed plugins/themes to those actually required and keeping them current lowers the chance a chain exists, at the cost of losing optional functionality. If the plugin is not actively used, deactivating and removing GS Logo Slider eliminates the exposure entirely.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-502, deserialization of untrusted data, in a PHP WordPress plugin. PHP's unserialize() does not by itself execute code, but when attacker-supplied serialized strings are passed to it, the attacker can control which classes are instantiated and how their magic methods (__wakeup, __destruct, __toString) are invoked, producing object injection. Achieving concrete impact typically requires chaining those object instantiations through classes already loaded in the request - a POP gadget chain - which may come from the plugin, WordPress core, or any other installed plugin or theme. The CPE cpe:2.3:a:gs_plugins:gs_logo_slider:*:*:*:*:*:*:*:* identifies the affected WordPress plugin across all versions through 3.8.9. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H indicates a network-reachable attack requiring low privileges, no user interaction, and high impact on all three confidentiality, integrity and availability pillars.
Know when Gs Logo Slider gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Network-reachable over HTTP (AV:N) with no special timing described (AC:L); a low-privilege account is required (PR:L) and no user interaction, with object injection yielding high C/I/A.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Deserialization of Untrusted Data vulnerability in GS Plugins GS Logo Slider gs-logo-slider allows Object Injection.This issue affects GS Logo Slider: from n/a through 3.8.9.
Executive ViewAI
CVE-2026-116391 is a high-severity PHP object injection vulnerability in the GS Logo Slider WordPress plugin (version 3.8.9 and earlier), enabling authenticated users with low-level privileges to potentially compromise site confidentiality, integrity, and availability. Given the widespread use of WordPress and third-party plugins, leadership should prioritize identification and mitigation of affected installations to prevent potential data breaches or site takeovers.
No vendor-released patch identified at time of analysis. Interim mitigations include disabling or removing the plugin, restricting low-privilege user accounts, and deploying WAF rules to detect and block object injection attempts.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.
EUVD-2026-112074
GHSA-mcxv-6x48-wcc3
NVD
CVE.org
Exploit-DB