LiveActive security incident?Get immediate response
CVE Record

CVE-2023-34006: WordPress Telegram Bot & Channel Plugin <= 3.6.2 is vulnerable to Cross Site Scripting (XSS)

Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in Marco Milesi Telegram Bot & Channel plugin <= 3.6.2 versions.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE affects the WordPress Telegram Bot & Channel plugin through version 3.6.2. An administrator-level user could store script content that later runs in another user’s browser. Business risk is moderate because exploitation requires high privileges and user interaction, but successful abuse can affect confidentiality, integrity, and availability in the WordPress admin context.

Executive priority

Prioritize during normal vulnerability remediation, faster for high-value WordPress sites or environments with many administrators. The issue is not known exploited from the supplied sources, but stored XSS in admin workflows can support account abuse and content tampering.

Technical view

CVE-2023-34006 is a stored cross-site scripting issue, CWE-79, in Marco Milesi Telegram Bot & Channel for WordPress <= 3.6.2. CVSS 3.1 is 5.9 with PR:H, UI:R, and scope changed. The source bundle does not identify the exact field, sink, exploit chain, or fixed version.

Likely exposure

Exposure is limited to WordPress sites running the Telegram Bot & Channel plugin at version 3.6.2 or earlier, especially where multiple administrator-level users or delegated site managers can access plugin settings.

Exploitation context

No CISA KEV listing or cited source indicates active exploitation. The CVSS vector says exploitation is network-reachable but requires administrator privileges and user interaction. Treat this as a governance and admin-session risk, not a broad unauthenticated internet-facing takeover issue.

Researcher notes

The evidence identifies authenticated admin-plus stored XSS but lacks vulnerable parameter details, exploit status, and fixed-release data. Avoid assuming unauthenticated exposure. Validation should focus on version inventory, plugin presence, admin-role review, and vendor advisory follow-up.

Mitigation direction

  • Inventory WordPress sites for the Telegram Bot & Channel plugin.
  • Treat plugin versions 3.6.2 and earlier as affected.
  • Check vendor or Patchstack guidance for a fixed release.
  • Disable the plugin if no supported fixed version is available.
  • Limit administrator access to trusted accounts only.
  • Review recent administrator activity for suspicious content changes.

Validation and detection

  • Confirm whether the plugin slug or package name telegram-bot is installed.
  • Record the installed plugin version on each WordPress site.
  • Flag any version 3.6.2 or earlier for remediation.
  • Verify administrative roles are restricted to necessary personnel.
  • Review vendor advisories for fixed-version confirmation.
  • Retest after update or removal to confirm exposure is gone.
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-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-34006 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.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/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
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.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L1.73.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/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
Marco MilesiTelegram Bot & Channeltelegram-bot, n/aunaffected
Weakness

CWE details

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