Skip to main content

GS Pins CVE-2026-110370

| EUVDEUVD-2026-107157 HIGH
Deserialization of Untrusted Data (CWE-502)
2026-10-21 Patchstack GHSA-p5v7-wwjh-3vhv
8.8
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate with low-privilege account
  2. Delivery
    Submit crafted serialized payload
  3. Exploit
    Trigger unserialize() object injection
  4. Execution
    Invoke PHP gadget chain
  5. Impact
    Execute code or compromise data

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

Exploitation requires the attacker to hold a valid authenticated WordPress account at low privilege (CVSS PR:L - e.g. Subscriber/Contributor level) on a site running GS Pins for Pinterest (gs-pinterest-portfolio) version 1.9.2 or earlier. The attacker must reach the plugin code path that passes attacker-controlled input to PHP unserialize(); successful impact (code execution vs. limited object injection) further depends on the availability of a usable POP gadget chain in the plugin, WordPress core, or another installed component. No user interaction is required (UI:N) and the attack is over the network (AV:N), but the authentication requirement and gadget-chain dependency are the primary factors limiting real-world exploitation.

Impact

This is a CWE-502 PHP Object Injection flaw with a vendor (Patchstack) CVSS 3.1 vector of AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (8.8, High). The network attack vector, low complexity, and no required user interaction make exploitation straightforward, and the full H/H/H impact reflects the typical outcome of successful PHP object injection - potential remote code execution, data theft, or site takeover when a usable POP gadget chain is present. The key limiting signal is PR:L: exploitation requires at least low-privileged authentication (commonly a Subscriber/Contributor-level WordPress account), so this is not a fully unauthenticated bug. No EPSS score, no CISA KEV listing, and no public POC were provided in the intelligence, so there is no evidence of active exploitation or weaponization at this time. Net assessment: a genuinely high-severity, easy-to-exploit vulnerability for any attacker who can obtain even a low-level account, but real-world mass-exploitation risk is tempered by the authentication requirement, the narrow deployment footprint of this specific plugin, and the dependency on a reachable gadget chain (the CVSS H/H/H assumes a worst-case gadget that may not exist in a default install).

Exploit ScenarioDerived

An attacker who holds or registers a low-privileged account on a WordPress site running GS Pins for Pinterest 1.9.2 or earlier submits a crafted serialized payload to a vulnerable plugin input that is passed to unserialize(). If a suitable PHP property-oriented programming (gadget) chain is available in the plugin, WordPress core, or another installed plugin/theme, the deserialization triggers object injection leading to data compromise or remote code execution. No public exploit code was identified in the provided data.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 21, 2026

PHP object injection in GS Pins for Pinterest 1.9.2 and earlier allows an authenticated low-privilege WordPress user to pass crafted serialized data into PHP unserialize(), potentially enabling object injection and, if a usable POP gadget chain exists, code execution or other high-impact actions. The flaw is rated CVSS 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), and no public exploit was identified at time of analysis. Sites running the plugin should treat low-privilege accounts as an attack prerequisite and remove or mitigate the plugin until a fix is confirmed.

RemediationAI

No vendor-released patch was identified at time of analysis, and no fixed version is specified in the supplied data; check the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/gs-pinterest-portfolio/vulnerability/wordpress-gs-pins-for-pinterest-plugin-1-9-2-php-object-injection-vulnerability?_s_id=cve for updated guidance. Until a patched release is confirmed, remove or disable GS Pins for Pinterest if it is not required; if it must remain, restrict creation and use of low-privilege WordPress accounts such as Subscriber and Contributor to trusted users and audit existing roles because PR:L is the required attack entry point. Deploy virtual patching or WAF rules that block serialized PHP object payloads directed at gs-pinterest-portfolio endpoints, recognizing possible false positives for legitimate plugin requests, and monitor logs for unusual requests to the plugin. Removing the plugin breaks Pinterest pin and portfolio functionality as a trade-off.

Affected VersionsENISA

GS Pins for Pinterest 0 ≤1.9.2

Affected Packages

euvd gs_pins_for_pinterest no fix

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 affected component is the WordPress plugin gs-pinterest-portfolio, identified by CPE cpe:2.3:a:gs_plugins:gs_pins_for_pinterest:*:*:*:*:*:*:*:* and described as affecting versions through 1.9.2. CWE-502 describes deserialization of untrusted data: attacker-controlled serialized input reaches a PHP unserialize()/object-injection path and can instantiate arbitrary classes. The CVSS vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H indicates network reachability, low attack complexity, no user interaction, and a requirement for a valid low-privilege WordPress account. Real impact depends on whether a usable POP gadget chain exists in the plugin, WordPress core, or another installed component, so object injection does not automatically guarantee remote code execution.

Know when Gs Pins For Pinterest 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

Vendor (Patchstack) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Network-reachable PHP object injection needing only a low-privileged account (PR:L), no interaction (UI:N), with potential full compromise via a gadget chain justifying C:H/I:H/A:H.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Deserialization of Untrusted Data vulnerability in GS Plugins GS Pins for Pinterest gs-pinterest-portfolio allows Object Injection.This issue affects GS Pins for Pinterest: from n/a through 1.9.2.

Executive ViewAI

Why It Matters

GS Pins for Pinterest versions 1.9.2 and earlier contain a high-severity PHP object injection flaw that gives any authenticated low-privilege WordPress account a potential path to code execution or other high-impact actions. Because no vendor patch is available and no public exploit has been identified at time of analysis, the immediate business risk is concentrated on sites that allow low-privilege users and run the affected plugin. Leadership should prioritize inventory, access tightening, and removal or isolation of the plugin until a fix is confirmed.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations include deactivating or removing GS Pins for Pinterest 1.9.2 and earlier, restricting and auditing low-privilege WordPress accounts, monitoring for suspicious serialized input, and applying virtual patching or WAF rules if available.

Threat Intelligence Overview

EPSS Score
0.5%
Top 57% exploitable
Prevalence
Low
niche single-purpose WordPress Pinterest portfolio plugin, limited install base
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.5%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

45
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy