Cool TimelineWordPress extension · Coolplugins
CVE-2022-4950
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSeveral WordPress plugins developed by Cool Plugins are vulnerable to arbitrary plugin installation and activation that can lead to remote code execution by authenticated attackers with minimal permissions, such as a subscriber.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisThe application checks who you are but not whether you're allowed to perform a given action, so any authenticated user can reach things meant for others. This is the classic “change the ID in the URL” bug. The fix is an authorization check on every request, evaluated against the acting user's permissions.
General guidance for the missing authorization class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Cool TimelineWordPress extension
< 2.4
Cryptocurrency WidgetsWordPress extension
< 2.5.1
Cryptocurrency Widgets For ElementorWordPress extension
< 1.3
Event Single Page Builder For The Event CalendarWordPress extension
< 1.6
Events Notification Bar AddonWordPress extension
< 1.6
Events Search For The Events CalendarWordPress extension
< 1.2
Events Shortcodes For The Events CalendarWordPress extension
< 2.0
Events Widgets For Elementor And The Events CalendarWordPress extension
< 1.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.21.31.5
Upgrade each plugin to its specified fixed version: Cool Timeline 2.4, Cryptocurrency Widgets 2.5.1, Cryptocurrency Widgets For Elementor 1.3, Event Single Page Builder For The Event Calendar 1.6, Events Notification Bar Addon 1.6, Events Search For The Events Calendar 1.2, Events Shortcodes For The
- 1. Audit your WordPress installation to identify all installed Cool Plugins (Cool Timeline, Cryptocurrency Widgets, Cryptocurrency Widgets For Elementor, Event Single Page Builder For The Event Calendar, Events Notification Bar Addon, Events Search For The Events Calendar, Events Shortcodes For The Events Calendar, Events Widgets For Elementor And The Events Calendar)
- 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
- 3. Update each affected plugin to its fixed version: Cool Timeline to 2.4, Cryptocurrency Widgets to 2.5.1, Cryptocurrency Widgets For Elementor to 1.3, Event Single Page Builder For The Event Calendar to 1.6, Events Notification Bar Addon to 1.6, Events Search For The Events Calendar to 1.2, Events Shortcodes For The Events Calendar to 2.0, Events Widgets For Elementor And The Events Calendar to
- 4. Alternatively, update all plugins via WordPress automatic updater or by downloading from wordpress.org
- 5. After updating, verify the version numbers in Plugins > Installed Plugins confirm the fixes are applied
- 6. Ensure no unauthorized administrator accounts have been added by reviewing Users > All Users
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-4950 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-4950 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data