My Calendar – Accessible Event Manager
Approved changes feed: RSS · Atom
cpe:2.3:a:joedolson:my_calendar_–_accessible_event_manager:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Joedolson (472b3ff9-b5b2-5b4f-afc5-43713b0252af) |
|---|---|
| Product | My Calendar – Accessible Event Manager (3e5dbeba-ea7b-5193-9676-f95e26e2ba89) |
| 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-2026-6854 |
vulnerable | 2026-07-29 01:06:21.264589 |
My Calendar <= 3.7.8 - Unauthenticated SQL Injection via 'mc_auth' and 'mc_host' Parameters
HIGH (7.5)
The My Calendar – Accessible Event Manager plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'mc_auth' parameter in all versions up to, and including, 3.7.8 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Published: 2026-07-08T11:30:33.597Z
Updated: 2026-07-08T13:14:04.081Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-11896 |
vulnerable | 2026-07-29 00:23:31.768502 |
My Calendar <= 3.7.14 - Insecure Direct Object Reference to Unauthenticated Sensitive Information Disclosure via 'vcal' Parameter
MEDIUM (5.3)
The My Calendar – Accessible Event Manager plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.7.14 via the 'vcal' parameter due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to enumerate occurrence IDs and access the full iCalendar export of non-public, draft, trashed, and personal calendar events, disclosing sensitive event metadata including titles, descriptions, dates, locations, organizer and host details, permalinks, and related calendar metadata.
Published: 2026-07-02T08:33:06.892Z
Updated: 2026-07-02T19:42:08.293Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-7525 |
vulnerable | 2026-06-08 08:08:57.368974 |
My Calendar <= 3.7.9 - Authenticated (Custom+) Missing Authorization to Unauthorized Event Publication via 'event_approved' Parameter
MEDIUM (4.3)
The My Calendar – Accessible Event Manager plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.7.9. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with custom-level access and above, to bypass the moderation and approval workflow by tampering with the POST body to publish events or set other unauthorized statuses such as cancelled or private, in ways their role does not permit. While the UI correctly restricts low-privilege users to a draft-only submit button, this restriction is enforced only client-side, making it trivially bypassable by directly manipulating the POST request.
Published: 2026-05-14T03:27:14.071Z
Updated: 2026-05-14T10:47:55.384Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-2355 |
vulnerable | 2026-06-08 07:55:16.949953 |
My Calendar – Accessible Event Manager <= 3.7.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode Attributes
MEDIUM (6.4)
The My Calendar – Accessible Event Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `template` attribute of the `[my_calendar_upcoming]` shortcode in all versions up to, and including, 3.7.3. This is due to the use of `stripcslashes()` on user-supplied shortcode attribute values in the `mc_draw_template()` function, which decodes C-style hex escape sequences (e.g., `\x3c` to `<`) at render time, bypassing WordPress's `wp_kses_post()` content sanitization that runs at save time. 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: 2026-03-04T11:22:29.620Z
Updated: 2026-04-08T16:33:01.860Z 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.