CVE-2024-2090: The Remote Content Shortcode plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions

Q: How do I fix CVE-2024-2090?

remote content shortcode: upgrade to newer than 1.5. Exact commands for each OS are on this page.

Q: Is CVE-2024-2090 being exploited?

CVE-2024-2090 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-2090 affect?

CVE-2024-2090 affects remote content shortcode. Severity is medium (CVSS 6.4). The Remote Content Shortcode plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.5 via the remote_content shortcode. This makes it possible for authenticated attackers, with contributor-

Q: How urgent is CVE-2024-2090?

Priority 27/100. No elevated risk signals yet.

Routine

MEDIUM 6.4UPGRADE

CVE-2024-2090 is a medium-severity flaw (CVSS 6.4) affecting remote content shortcode. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Remote Content Shortcode plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.5 via the remote_content shortcode. This makes it possible for authenticated attackers, with contributor-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 82%)
CISA exploited list	No
Weakness	CWE-918
Published	2024-08-01
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: doublesharp

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-08-01 05:15 UTCPublished CVE record published
2026-06-17 07:23 UTCUpdated Record last modified

doublesharp remote content shortcode UPGRADE

Affected: <= 1.5

Fixed in: newer than 1.5

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy remote-content-shortcode || rpm -q remote-content-shortcode || remote-content-shortcode --version

2. UPGRADE to newer than 1.5 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade remote-content-shortcode

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade remote-content-shortcode

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-2090?

remote content shortcode: upgrade to newer than 1.5. Exact commands for each OS are on this page.

Is CVE-2024-2090 being exploited?

CVE-2024-2090 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-2090 affect?

CVE-2024-2090 affects remote content shortcode. Severity is medium (CVSS 6.4). The Remote Content Shortcode plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.5 via the remote_content shortcode. This makes it possible for authenticated attackers, with contributor-

How urgent is CVE-2024-2090?

Priority 27/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs