dbcve.org
Gs Pinterest PortfolioWordPress extension · Gsplugins

CVE-2024-30192

MEDIUM · 6.5 CVSS v3.1 Published 2024-03-27
Fix available
A fix is available. Upgrade to 1.8.3 or later.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in GS Plugins GS Pins for Pinterest allows Stored XSS.This issue affects GS Pins for Pinterest: from n/a through 1.8.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Stored Cross-site Scripting (XSS) vulnerability in GS Pins for Pinterest plugin allows authenticated attackers to inject malicious JavaScript code through plugin input fields. The malicious script is stored on the server and executes when other users view affected pages, potentially leading to session hijacking or credential theft.

MitigationUpdate GS Pins for Pinterest to the latest version after confirming a patch is available. If no patch exists, remove the plugin from production environments until a fix is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Gs Pinterest PortfolioWordPress extension
Affected:< 1.8.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the GS Pinterest Portfolio plugin installation
    Check your WordPress plugins directory at wp-content/plugins/gs-pinterest-portfolio/ or look for the plugin in the WordPress admin under Plugins > Installed Plugins
    Affected if The plugin directory gs-pinterest-portfolio/ exists on the server
  2. Identify the installed plugin version
    Open the main plugin file (usually gs-pinterest-portfolio.php) and locate the Version header in the plugin comment block, or check the version listed in the WordPress admin plugins list
    Affected if The version displayed is less than 1.8.3 (for example: 1.8.2, 1.8.1, 1.8.0, or any version before 1.8.3)
  3. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify the GS Pinterest Portfolio plugin is activated, or query the wp_options table for option_name = 'active_plugins'
    Affected if The plugin shows as Active in WordPress or is present in the active_plugins array
  4. Check for authenticated user access to plugin settings
    Review WordPress user roles that have access to the plugin settings pages (usually under GS Plugins > Pinterest Settings) by examining user capabilities or checking if non-admin users can access plugin admin menus
    Affected if Users with Subscriber, Contributor, or Author roles can access the plugin input fields

You are affected if GS Pinterest Portfolio plugin version is below 1.8.3, the plugin is currently active, and authenticated users can access the plugin input fields where malicious JavaScript can be stored.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.8.3 or later
Fixed in 1.8.3
Interim mitigation

Update GS Pins for Pinterest to the latest version after confirming a patch is available. If no patch exists, remove the plugin from production environments until a fix is released.

Recommended fix High confidence

GS Pinterest Portfolio version 1.8.3

  1. 1. Create a complete backup of your WordPress site (database and files) before making any changes
  2. 2. Navigate to your WordPress admin dashboard > Plugins > Installed Plugins
  3. 3. Find 'GS Pinterest Portfolio' (or 'GS Pins for Pinterest') in the plugin list
  4. 4. Click 'Update now' if an update is available, or manually update to version 1.8.3
  5. 5. After updating, verify the plugin version shows 1.8.3 in the Plugins list
  6. 6. Test the Pinterest portfolio functionality to ensure the plugin works correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gs Pinterest Portfolio Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-30192 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-30192 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data