Contextual Related Posts at a glance
- 11 publicly disclosed vulnerabilities, 2 of them rated High or Critical. The most recent was disclosed on Nov 7, 2026.
- Ranked #736 by popularity on WordPress.org (50,000+ active installs).
- The latest version is 4.5.7 (released Nov 21, 2026). The most recent security fix shipped in 4.5.4.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Contextual Related Posts version
Enter the Contextual Related Posts version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Contextual Related Posts”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Contextual Related Posts”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (4.5.7). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Contextual Related Posts vulnerabilities
Contextual Related Posts <= 4.5.3 - Missing Authorization
Missing authorization · CVE-2026-121724
Affected versions: ≤ 4.5.3
Fixed in: 4.5.4
Severity: Medium 4.3 · Disclosed Nov 7, 2026
Contextual Related Posts <= 4.4.1 - Authenticated (Author+) Stored Cross-Site Scripting via 'other_attributes' Block Parameter
Cross-site scripting (XSS) · CVE-2026-85653
Affected versions: ≤ 4.4.1
Fixed in: 4.4.2
Severity: Medium 6.4 · Disclosed Sep 21, 2026
Contextual Related Posts <= 4.2.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'other_attributes'
Cross-site scripting (XSS) · CVE-2026-2986
Affected versions: ≤ 4.2.1
Fixed in: 4.2.2
Severity: Medium 6.4 · Disclosed Apr 17, 2026
Contextual Related Posts < 4.2.2 - Missing Authorization
Missing authorization · CVE-2026-32565
Affected versions: < 4.2.2
Fixed in: 4.2.2
Severity: Medium 5.3 · Disclosed Mar 18, 2026
Contextual Related Posts <= 4.0.2 - Authenticated (Contributor+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2025-47506
Affected versions: ≤ 4.0.2
Fixed in: 4.0.3
Severity: Medium 6.4 · Disclosed May 7, 2025
Contextual Related Posts <= 3.3.1 - Missing Authorization in crp_ajax_clearcache
Missing authorization
Affected versions: ≤ 3.3.1
Fixed in: 3.3.2
Severity: Medium 4.3 · Disclosed Feb 20, 2023
Contextual Related Posts <= 3.3.1 - Cross-Site Request Forgery in crpClearCache
Cross-site request forgery (CSRF)
Affected versions: ≤ 3.3.1
Fixed in: 3.3.2
Severity: Medium 4.3 · Disclosed Feb 20, 2023
Contextual Related Posts <= 3.3.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via Block Attribute
Cross-site scripting (XSS) · CVE-2023-0252
Affected versions: ≤ 3.3.0
Fixed in: 3.3.1
Severity: Medium 6.4 · Disclosed Jan 5, 2023
Contextual Related Posts <= 2.9.3 - Cross-Site Request Forgery
Cross-site request forgery (CSRF)
Affected versions: ≤ 2.9.3
Fixed in: 2.9.4
Severity: Medium 4.3 · Disclosed Nov 19, 2020
Contextual Related Posts <= 1.8.6 - Cross-Site Request Forgery to Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2013-2710
Affected versions: ≤ 1.8.6
Fixed in: 1.8.7
Severity: High 8.8 · Disclosed Aug 1, 2014
Contextual Related Posts < 1.8.10.2 - SQL Injection
SQL injection · CVE-2014-3937
Affected versions: < 1.8.10.2
Fixed in: 1.8.10.2
Severity: Critical 9.8 · Disclosed Mar 6, 2014
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Contextual Related Posts <= 4.5.3 - Missing AuthorizationMissing authorization · CVE-2026-121724 | ≤ 4.5.3 | 4.5.4 | Medium 4.3 | Nov 7, 2026 |
| Contextual Related Posts <= 4.4.1 - Authenticated (Author+) Stored Cross-Site Scripting via 'other_attributes' Block ParameterCross-site scripting (XSS) · CVE-2026-85653 | ≤ 4.4.1 | 4.4.2 | Medium 6.4 | Sep 21, 2026 |
| Contextual Related Posts <= 4.2.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'other_attributes'Cross-site scripting (XSS) · CVE-2026-2986 | ≤ 4.2.1 | 4.2.2 | Medium 6.4 | Apr 17, 2026 |
| Contextual Related Posts < 4.2.2 - Missing AuthorizationMissing authorization · CVE-2026-32565 | < 4.2.2 | 4.2.2 | Medium 5.3 | Mar 18, 2026 |
| Contextual Related Posts <= 4.0.2 - Authenticated (Contributor+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2025-47506 | ≤ 4.0.2 | 4.0.3 | Medium 6.4 | May 7, 2025 |
| Contextual Related Posts <= 3.3.1 - Missing Authorization in crp_ajax_clearcacheMissing authorization | ≤ 3.3.1 | 3.3.2 | Medium 4.3 | Feb 20, 2023 |
| Contextual Related Posts <= 3.3.1 - Cross-Site Request Forgery in crpClearCacheCross-site request forgery (CSRF) | ≤ 3.3.1 | 3.3.2 | Medium 4.3 | Feb 20, 2023 |
| Contextual Related Posts <= 3.3.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via Block AttributeCross-site scripting (XSS) · CVE-2023-0252 | ≤ 3.3.0 | 3.3.1 | Medium 6.4 | Jan 5, 2023 |
| Contextual Related Posts <= 2.9.3 - Cross-Site Request ForgeryCross-site request forgery (CSRF) | ≤ 2.9.3 | 2.9.4 | Medium 4.3 | Nov 19, 2020 |
| Contextual Related Posts <= 1.8.6 - Cross-Site Request Forgery to Cross-Site ScriptingCross-site scripting (XSS) · CVE-2013-2710 | ≤ 1.8.6 | 1.8.7 | High 8.8 | Aug 1, 2014 |
| Contextual Related Posts < 1.8.10.2 - SQL InjectionSQL injection · CVE-2014-3937 | < 1.8.10.2 | 1.8.10.2 | Critical 9.8 | Mar 6, 2014 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Nov 7, 2026.
Most common weaknesses in Contextual Related Posts
Cross-site scripting (XSS)
5 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Missing authorization
3 issues
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
Cross-site request forgery (CSRF)
2 issues
If an administrator who is logged in opens a booby-trapped page elsewhere, the site can be made to change settings without their knowledge.
Frequently asked questions
Is Contextual Related Posts safe to use?
Contextual Related Posts is a well-known plugin with 50,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (4.5.7) and turn on automatic updates.
How do I find which version of Contextual Related Posts my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.
← All plugin vulnerabilitiesContextual Related Posts on WordPress.org