Firecask’S Twitter Follow Button
Approved changes feed: RSS · Atom
cpe:2.3:a:alexmoss:firecask’s_twitter_follow_button:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Alexmoss (13922652-9a39-59a0-a237-66b890a9b541) |
|---|---|
| Product | Firecask’S Twitter Follow Button (b5101911-b228-5b62-b7d4-95e0252169eb) |
| 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-2024-10116 |
vulnerable | 2026-06-08 06:22:03.599427 |
Twitter Follow Button <= 0.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via username Parameter
MEDIUM (6.4)
The Twitter Follow Button plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'username' parameter in all versions up to, and including, 0.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Published: 2024-11-23T03:25:52.398Z
Updated: 2026-04-08T17:34:26.435Z Reference links
|
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.