Telegram For Wp
Approved changes feed: RSS · Atom
cpe:2.3:a:amir-mousavi:telegram_for_wp:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Amir Mousavi (2cfbcf3f-0a43-5419-bc55-c29bca45bd33) |
|---|---|
| Product | Telegram For Wp (80c4f2b8-b5de-5a22-b603-6c95bcc44c16) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-5939 |
vulnerable | 2026-06-08 07:37:26.113076 |
Telegram for WP <= 1.6.1 - Authenticated (Admin+) Stored Cross-Site Scripting
MEDIUM (4.4)
The Telegram for WP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1.6.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.
Published: 2025-06-13T01:47:50.112Z
Updated: 2026-04-08T17:24:38.135Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.