LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32519: WordPress Bit SMTP plugin <= 1.2.2 - Broken Authentication vulnerability

Incorrect Privilege Assignment vulnerability in Bit Apps Bit SMTP bit-smtp allows Privilege Escalation.This issue affects Bit SMTP: from n/a through <= 1.2.2.

CriticalCVSS 9Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-32519 affects the WordPress Bit SMTP plugin through version 1.2.2. The issue is described as broken authentication and incorrect privilege assignment that can allow privilege escalation. For organizations running this plugin, the business risk is high because the CVSS rating indicates possible full confidentiality, integrity, and availability impact.

Executive priority

Prioritize this as a critical WordPress plugin risk where Bit SMTP is present. The main decision is rapid inventory and containment, because the available sources do not identify a patch. Sites not running Bit SMTP are not indicated as affected.

Technical view

The CVE describes CWE-266 in Bit Apps Bit SMTP, package bit-smtp, affecting versions through <= 1.2.2. CVSS 3.1 is 9.0 with AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H. The advisory indicates unauthenticated network exploitation is possible, but with high attack complexity. No fixed version is provided in the supplied sources.

Likely exposure

Exposure is most likely on internet-facing WordPress sites that have Bit SMTP installed at version 1.2.2 or earlier. The source bundle does not provide CPEs, install counts, vulnerable endpoint details, or hosting-specific exposure conditions.

Exploitation context

The CVE is public and referenced by Patchstack. The source bundle does not state active exploitation, and it is not listed as KEV. Treat it as urgent because exploitation requires no account or user interaction, though attack complexity is rated high.

Researcher notes

Evidence is sparse. The public record names broken authentication, privilege escalation, CWE-266, and CVSS metrics, but does not provide exploit mechanics, a fixed version, or detailed preconditions. Avoid exploit validation; focus on version confirmation, vendor tracking, and post-exposure review.

Mitigation direction

  • Identify all WordPress sites using the Bit SMTP plugin.
  • Check whether Bit SMTP is version 1.2.2 or earlier.
  • Check Bit Apps and Patchstack for a fixed release or official workaround.
  • If operationally acceptable, disable or remove the plugin until vendor guidance is available.
  • Prioritize remediation for public-facing or business-critical WordPress sites.

Validation and detection

  • Confirm installed Bit SMTP versions from WordPress plugin inventory.
  • Verify whether any vendor update is available and successfully applied.
  • Review WordPress users and roles for unexpected privilege changes.
  • Review site logs for suspicious unauthenticated activity around plugin endpoints.
  • Document systems where the plugin remains installed and why.
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 · low confidence lookup

CWE-266: 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

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior 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-32519 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
Critical
CVSS
9 (3.1)
Known Exploited
No
Published

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

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
9CVSS 3.1CriticalCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H2.26Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9Critical
CVSS 3.1 vector shape for CVE-2026-32519Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
Bit AppsBit SMTPbit-smtp, n/aunaffected
Weakness

CWE details

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

CWE-266 · source CWE mapping

Incorrect Privilege Assignment

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