LiveActive security incident?Get immediate response
CVE Record

CVE-2025-68035: WordPress Tabby Checkout plugin <= 5.8.4 - Sensitive Data Exposure vulnerability

Insertion of Sensitive Information Into Sent Data vulnerability in tabbyai Tabby Checkout tabby-checkout allows Retrieve Embedded Sensitive Data.This issue affects Tabby Checkout: from n/a through <= 5.8.4.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-68035 affects the WordPress Tabby Checkout plugin through version 5.8.4. The issue may expose sensitive embedded data to an unauthenticated remote attacker. For businesses using this checkout plugin, the main risk is confidentiality: leaked data could create customer trust, privacy, and payment-operation concerns.

Executive priority

Prioritize this for any internet-facing commerce site using Tabby Checkout. The issue is high severity and requires no authentication, but evidence of active exploitation and a confirmed fixed version were not provided.

Technical view

The CVE describes CWE-201, insertion of sensitive information into sent data, in tabbyai Tabby Checkout for WordPress. CVSS 3.1 is 7.5: network exploitable, low complexity, no privileges, no user interaction, high confidentiality impact, no integrity or availability impact.

Likely exposure

Public WordPress sites running Tabby Checkout versions up to and including 5.8.4 are the likely exposure. The sources do not identify a fixed version, vulnerable endpoint, required configuration, or exact data type exposed.

Exploitation context

The CVE is not marked as CISA KEV in the provided data. No provided source states active exploitation. The CVSS vector indicates exploitation could be remote and unauthenticated if a site runs an affected plugin version.

Researcher notes

Evidence is limited to CVE and Patchstack summaries. The affected range is stated as through 5.8.4, but the bundle does not include technical details, proof-of-concept, indicators, or remediation specifics. Avoid assuming payment card exposure without vendor confirmation.

Mitigation direction

  • Inventory WordPress sites for the Tabby Checkout plugin and record installed versions.
  • If installed version is 5.8.4 or older, check vendor or Patchstack guidance immediately.
  • Update to a vendor-confirmed fixed version when available.
  • If no fix is available, consider disabling the plugin where business impact allows.
  • Review checkout data exposure and retention assumptions with application owners.

Validation and detection

  • Confirm plugin slug tabby-checkout is present on each WordPress instance.
  • Verify the installed Tabby Checkout version is greater than 5.8.4, if available.
  • Check vendor, WordPress plugin, and Patchstack pages for fixed-version information.
  • Review web and application logs for unusual unauthenticated access patterns.
  • Document whether the plugin processes or displays sensitive checkout-related data.
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-2025-68035 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2025-68035Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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
tabbyaiTabby Checkouttabby-checkout, 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.