CVE-2023-6991: The JSM file_get_contents() Shortcode WordPress plugin before 2.7.1 does not validate one of its shortcode's p

Q: How do I fix CVE-2023-6991?

jsm file get contents\(\) shortcode: upgrade to 2.7.1. Exact commands for each OS are on this page.

Q: Is CVE-2023-6991 being exploited?

CVE-2023-6991 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-2023-6991 affect?

CVE-2023-6991 affects jsm file get contents\(\) shortcode. Severity is high (CVSS 8.8). The JSM file_get_contents() Shortcode WordPress plugin before 2.7.1 does not validate one of its shortcode's parameters before making a request to it, which could allow users with contributor role and above to perform SSRF attacks.

Q: How urgent is CVE-2023-6991?

Priority 49/100. High severity; Public exploit reference

This month

HIGH 8.8UPGRADE

CVE-2023-6991 is a high-severity flaw (CVSS 8.8) affecting jsm file get contents\(\) shortcode. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The JSM file_get_contents() Shortcode WordPress plugin before 2.7.1 does not validate one of its shortcode's parameters before making a request to it, which could allow users with contributor role and above to perform SSRF attacks.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.7% (top 47%)
CISA exploited list	No
Weakness	CWE-918
Published	2024-01-15
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: surniaulula

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

Am I affected?

Timeline

2024-01-15 16:15 UTCPublished CVE record published
2026-06-17 06:51 UTCUpdated Record last modified

surniaulula jsm file get contents\(\) shortcode UPGRADE

Affected: < 2.7.1

Fixed in: 2.7.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy jsm-file-get-contents-shortcode || rpm -q jsm-file-get-contents-shortcode || jsm-file-get-contents-shortcode --version

2. UPGRADE to 2.7.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade jsm-file-get-contents-shortcode

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade jsm-file-get-contents-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-2023-6991?

jsm file get contents\(\) shortcode: upgrade to 2.7.1. Exact commands for each OS are on this page.

Is CVE-2023-6991 being exploited?

CVE-2023-6991 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-2023-6991 affect?

CVE-2023-6991 affects jsm file get contents\(\) shortcode. Severity is high (CVSS 8.8). The JSM file_get_contents() Shortcode WordPress plugin before 2.7.1 does not validate one of its shortcode's parameters before making a request to it, which could allow users with contributor role and above to perform SSRF attacks.

How urgent is CVE-2023-6991?

Priority 49/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs