CVE-2024-11765 MEDIUM

CVE-2024-11765: WordPress Portfolio Plugin – A Plugin for Making Filterable Portfolio Grid, Portfolio Slider and more <= 1.6.3 - Authenticated (Contributor+) Stored Cross-Site Scripting

Vendor Samdani
Product GS Portfolio – A Plugin for Making Filterable Portfolio Grid, Portfolio Slider and more
Weakness CWE-79 · XSS
Published December 12, 2024
Last update April 8, 2026

CVSS base score

6.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

The WordPress Portfolio Plugin – A Plugin for Making Filterable Portfolio Grid, Portfolio Slider and more plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'gs_portfolio' shortcode in all versions up to, and including, 1.6.3 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Explanation of Vulnerability in Simple Terms

02Summary

GS Portfolio versions up to 1.6.3 contain a stored cross-site scripting (XSS) vulnerability. An authenticated user with low privileges can inject malicious scripts into portfolio data that execute in the browsers of other site visitors. The vulnerability affects the scope beyond the plugin itself, potentially compromising site security and user data.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that run in other users' browsers when they view portfolio content.

Potential impact on your site

04Site Impact

Visitors to your site may have their sessions hijacked, credentials stolen, or be redirected to malicious sites.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege authenticated account on the site.

Key dates

06Disclosure timeline

December 12, 2024 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE