Custom Content Shortcode vulnerabilities
Plugin slug custom-content-shortcode · 5 known vulnerabilities · latest disclosed 2023-02-22 · WordPress.org page
2 vulnerabilities have no fixed version yet. If you use this plugin, consider disabling or replacing it until a fix is released.
1 of 5 rated high or critical (CVSS 7 or more).
Known vulnerabilities in Custom Content Shortcode
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| Medium 6.4 | <= 4.0.2 | No fix yet | CVE-2023-0273 | 2023-02-22 | Advisory |
| High 8.8 | <= 4.0.2 | No fix yet | CVE-2023-0340 | 2023-02-22 | Advisory |
| Medium 5.4 | <= 4.0.1 | 4.0.2 | CVE-2021-24826 | 2022-02-02 | Advisory |
| Medium 4.3 | <= 3.8.8 | 4.0.1 | CVE-2021-24824 | 2022-02-02 | Advisory |
| Medium 4.3 | <= 4.0.1 | 4.0.2 | CVE-2021-24825 | 2022-02-02 | Advisory |
Check if a site is affected
Enter a site address to see which version of Custom Content Shortcode and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the Custom Content Shortcode plugin safe to use?
2 known issue(s) have no fix yet, so check the table above before using it.
How do I check which version of Custom Content Shortcode my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.