LiveActive security incident?Get immediate response
CVE Record

CVE-2023-6638: GTG Product Feed for Shopping <= 1.2.4 - Missing Authorization to Unauthenticated Plugin Settings Update

The GTG Product Feed for Shopping plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'update_settings' function in versions up to, and including, 1.2.4. This makes it possible for unauthenticated attackers to update plugin settings.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This WordPress plugin flaw lets someone who is not logged in change plugin settings. The main business risk is unauthorized feed or configuration changes that could disrupt shopping-feed operations or alter how product data is published. The source bundle does not show confirmed active exploitation.

Executive priority

Prioritize remediation for ecommerce or marketing sites that depend on shopping feeds. The issue is not rated critical, but unauthenticated settings changes can disrupt revenue-supporting product channels and should be handled in the next normal patch cycle or sooner for public-facing stores.

Technical view

CVE-2023-6638 is a CWE-862 missing authorization issue in the GTG Product Feed / GG Woo Feed plugin’s update_settings function through version 1.2.4. The CVSS 3.1 score is 6.5, reflecting network access, no authentication, no user interaction, low integrity impact, and low availability impact.

Likely exposure

Exposure is most likely on WordPress sites running GG Woo Feed for WooCommerce Shopping Feed on Google and Other Channels, also described as GTG Product Feed for Shopping, at version 1.2.4 or earlier.

Exploitation context

The bundle states unauthenticated attackers can update plugin settings. It does not include exploit code, proof of exploitation, or a KEV listing. Treat exposure as remotely reachable wherever vulnerable WordPress sites expose the affected plugin functionality.

Researcher notes

The strongest evidence is the CVE description, Wordfence advisory, and WordPress Trac references to affected code and a later changeset. The bundle does not identify active exploitation, detailed fix version, or confidentiality impact. Validate against vendor release history before asserting a specific fixed release.

Mitigation direction

  • Inventory WordPress sites for the affected plugin and installed version.
  • Update to a vendor-released version newer than 1.2.4 when available.
  • If no fixed version is available, disable or remove the plugin.
  • Review plugin settings for unauthorized or unexpected changes.
  • Monitor vendor and Wordfence guidance for fixed-version confirmation.

Validation and detection

  • Confirm whether the plugin slug gg-woo-feed is installed.
  • Flag installed versions up to and including 1.2.4.
  • Review web logs for unauthenticated access to plugin settings actions.
  • Verify updated code enforces authorization before settings changes.
  • Check product-feed configuration and outputs for unexpected modifications.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-6638 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L3.92.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2023-6638Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
wpopalGG Woo Feed for WooCommerce Shopping Feed on Google and Other Channels0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.