LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24589: WordPress Cargus plugin <= 1.5.8 - Sensitive Data Exposure vulnerability

Insertion of Sensitive Information Into Sent Data vulnerability in Cargus eCommerce Cargus cargus allows Retrieve Embedded Sensitive Data.This issue affects Cargus: from n/a through <= 1.5.8.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24589 is a medium-severity information exposure issue in the WordPress Cargus plugin through version 1.5.8. An unauthenticated remote attacker may be able to retrieve sensitive data embedded in sent information. The public sources do not name the specific data exposed or confirm active exploitation.

Executive priority

Treat as a targeted medium-priority WordPress exposure issue. It is not currently supported as actively exploited in the provided sources, but unauthenticated remote access and possible sensitive data leakage justify prompt inventory and remediation review for affected ecommerce sites.

Technical view

The CVE describes CWE-201, insertion of sensitive information into sent data, affecting Cargus eCommerce Cargus WordPress plugin versions up to 1.5.8. CVSS 3.1 is 5.3: network-accessible, low complexity, no privileges, no user interaction, unchanged scope, low confidentiality impact, no integrity or availability impact.

Likely exposure

Exposure is limited to WordPress sites running the Cargus plugin at version 1.5.8 or earlier. Sites not using this plugin are not affected based on available sources. Public metadata contains some version-record inconsistency, so asset owners should verify installed plugin identity and version directly.

Exploitation context

The CVSS vector indicates remote, unauthenticated access may be sufficient. The issue is not listed as KEV in the provided data, and the sources do not state that exploitation is active. No public exploit details are included in the provided source bundle.

Researcher notes

Evidence is sparse. The CVE and Patchstack entry identify the weakness class and affected plugin range, but do not specify exposed data, endpoint behavior, exploit status, or a fixed version in the provided bundle. The affected record also shows version metadata that appears inconsistent with the narrative description.

Mitigation direction

  • Inventory WordPress sites for the Cargus plugin and installed version.
  • Prioritize review of installations at version 1.5.8 or earlier.
  • Check Patchstack and vendor guidance for an available fixed version or mitigation.
  • Disable or restrict the plugin if sensitive data exposure risk is unacceptable.
  • Review exposed logs, responses, or integrations for unintended sensitive data disclosure.

Validation and detection

  • Confirm whether the Cargus plugin is installed on each WordPress site.
  • Record the exact plugin version from WordPress administration or asset inventory.
  • Compare installed versions against the affected range: through 1.5.8.
  • Review vendor or Patchstack advisories for updated remediation status.
  • Check web responses and integration outputs for unintended sensitive fields.
Prepared
Confidence
medium
Sources
3

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-201: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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-2026-24589 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
5.3 (3.1)
Known Exploited
No
Published

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

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
2Source 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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-24589Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
Cargus eCommerceCarguscargus, 0unaffected
Weakness

CWE details

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

CWE-201 · source CWE mapping

Insertion of Sensitive Information Into Sent Data

Insertion of Sensitive Information Into Sent Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.