LiveActive security incident?Get immediate response
CVE Record

CVE-2026-3546: e-shot <= 1.0.2 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Exposure via API Token via 'eshot_form_builder_get_account_data' AJAX Action

The e-shot form builder plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.0.2. The eshot_form_builder_get_account_data() function is registered as a wp_ajax_ AJAX handler accessible to all authenticated users. The function lacks any capability check (e.g., current_user_can('manage_options')) and does not verify a nonce. It directly queries the database for the e-shot API token stored in the eshotformbuilder_control table and returns it along with all subaccount data as a JSON response. This makes it possible for authenticated attackers, with Subscriber-level access and above, to extract the e-shot API token and subaccount information, which could then be used to access the victim's e-shot platform account.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-3546 affects the WordPress e-shot form builder plugin through version 1.0.2. A logged-in low-privilege user could access an API token and subaccount information because an AJAX function lacks authorization and nonce checks. This could expose the organization’s e-shot account. Public sources do not name a fixed version or active exploitation.

Executive priority

Treat as a near-term remediation item for sites with user registration or many low-privilege accounts. Prioritize token rotation and plugin update guidance where the e-shot account supports marketing or customer communications.

Technical view

The vulnerable eshot_form_builder_get_account_data() AJAX handler is registered for authenticated users and returns data from the eshotformbuilder_control table. Sources state it lacks a capability check and nonce verification, allowing Subscriber-level users or higher to retrieve the e-shot API token and subaccount data. Classified as CWE-202 sensitive information exposure, CVSS 3.1 score 5.3.

Likely exposure

WordPress sites using e-shot form builder versions up to and including 1.0.2 are potentially exposed, especially if untrusted users can create or hold Subscriber-level accounts.

Exploitation context

Sources describe a low-complexity authenticated information exposure. No CISA KEV listing or cited source confirms active exploitation. The main risk is credential exposure leading to unauthorized access to the victim’s e-shot platform account.

Researcher notes

The source bundle has an inconsistency: the narrative requires authenticated Subscriber-level access, while the CVSS vector lists PR:N. The WordPress wp_ajax context supports authenticated access. No fixed version is identified in the supplied sources.

Mitigation direction

  • Check vendor and WordPress plugin guidance for an updated fixed release.
  • Disable or remove the plugin if it is not business-critical.
  • Limit WordPress account creation and remove unnecessary Subscriber-level users.
  • Rotate the e-shot API token if exposure is suspected.
  • Review e-shot account activity for unauthorized access or changes.

Validation and detection

  • Inventory WordPress sites for e-shot form builder installed versions.
  • Flag versions up to and including 1.0.2 for remediation review.
  • Confirm low-privilege users cannot access e-shot account data after remediation.
  • Review plugin code or vendor notes for capability and nonce checks.
  • Check logs for unusual authenticated access to plugin AJAX actions.
Prepared
Confidence
high
Sources
7

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 · low confidence lookup

CWE-202: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-3546 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
6Source 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-3546Attack 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
forfronte-shot0unaffected
Weakness

CWE details

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

CWE-202 · source CWE mapping

Exposure of Sensitive Information Through Data Queries

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