CVE-2023-0890· NVD / CVE Program· CNA WPScan

Shortcodes Ultimate < 5.12.8 - Subscriber+ Arbitrary Post Access

Noroxi assessment

Priority: Monitor (action score 26/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.65% (FIRST EPSS); higher than 50.6% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

The WordPress Shortcodes Plugin — Shortcodes Ultimate WordPress plugin before 5.12.8 does not ensure that posts to be displayed via some shortcodes are already public and can be accessed by the user making the request, allowing any authenticated users such as subscriber to view draft, private or even password protected posts. It is also possible to leak the password of protected posts

MediumCVSS 6.5 · v3.1—No exploit No fix recorded

Broken access control (IDOR)

Published: Mar 20, 2023
Updated: Jun 17, 2026
EPSS: 0.6% · 50th percentile
CWE: CWE-862

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.6%

CISA SSVC decision

Exploitation: proof of concept
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Is Shortcodes Ultimate – Content Elements on your site?

WP Lens reads your site's plugin, theme and WordPress versions from the outside and matches them to known vulnerabilities. Works without an account.

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
getshortcodes	shortcodes ultimate	cpe:2.3:a:getshortcodes:shortcodes_ultimate

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

getshortcodes shortcodes ultimatebefore 5.12.8

Versions reported by the vendor

Affected version ranges reported by the assigning authority (WPScan). Independent of NVD's CPE analysis and usually ahead of it.

Unknown WordPress Shortcodes Plugin — Shortcodes Ultimate
- before 5.12.8affected

Same product

getshortcodes: all records

Other highest-scoring records for the same primary product.

CVE-2017-18580The shortcodes-ultimate plugin before 5.0.1 for WordPress has remote code execution via a filter in a meta, post, or user shortcode.
43Plan
CVE-2022-41136WordPress Shortcodes Ultimate plugin <= 5.12.0 - CSRF vulnerability leading to Stored XSS
35Monitor
CVE-2023-23800WordPress Shortcodes Ultimate Plugin <= 5.12.6 is vulnerable to Server Side Request Forgery (SSRF)
26Monitor

Published before and after this one in the same product

← EarlierCVE-2021-24525Sep 20, 2021 · Shortcodes Ultimate < 5.10.2 - Contributor+ Stored XSS
21Monitor
← EarlierCVE-2022-38086Oct 11, 2022 · WordPress Shortcodes Ultimate plugin <= 5.12.0 - Cross-Site Request Forgery (CSRF) vulnerability
17Monitor
Later →CVE-2023-0911Mar 20, 2023 · Shortcodes Ultimate < 5.12.8 - Subscriber+ User Meta Disclosure
26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

WPScancoordinator
Erwan LR (WPScan)finder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).