dbcve.org
Olevmedia ShortcodesWordPress extension · Olevmedia

CVE-2023-25798

MEDIUM · 5.4 CVSS v3.1 Published 2023-05-03
Fix available
A fix is available. Upgrade to after 1.1.9 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Olevmedia Olevmedia Shortcodes plugin <= 1.1.9 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Stored XSS vulnerability in Olevmedia Shortcodes WordPress plugin allowing authenticated users with contributor-level or higher permissions to inject malicious JavaScript through plugin shortcodes that persists in the database and executes when other users view affected content.

MitigationUpdate Olevmedia Shortcodes plugin to version greater than 1.1.9; if no patched version available, disable the plugin until a fix is released, or manually add input sanitization and output encoding to plugin code.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Olevmedia ShortcodesWordPress extension
Affected:<= 1.1.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin installation and version
    Navigate to WordPress Admin > Plugins > Installed Plugins and locate 'Olevmedia Shortcodes' in the list. Check the version number displayed under the plugin name. Alternatively, inspect the plugin's main PHP file (wp-content/plugins/olevmedia-shortcodes/olevmedia-shortcodes.php) or readme.txt for the Version header.
    Affected if The installed version is 1.1.9 or lower.
  2. Confirm plugin is active
    In the Plugins list, verify that the 'Olevmedia Shortcodes' plugin shows as 'Active' under its name.
    Affected if The plugin is active and the version is 1.1.9 or lower.
  3. Identify user roles with contributor access
    Navigate to WordPress Admin > Users > Users list. Review the 'Role' column to identify accounts with 'Contributor', 'Author', 'Editor', or 'Administrator' roles. These users can create or edit content containing shortcodes.
    Affected if Any user with contributor-level or higher permissions exists in the system.
  4. Scan database for plugin shortcode content
    Query the WordPress database (wp_posts table) for content containing the plugin's shortcode tags. Typical shortcode patterns include [om_shortcode] or similar. Use SQL: SELECT ID, post_title, post_content FROM wp_posts WHERE post_content LIKE '%[om_%' AND post_status IN ('publish', 'draft');
    Affected if Any posts or pages contain shortcodes from this plugin.
  5. Inspect shortcode content for suspicious patterns
    Examine the shortcode content found in the previous step. Look for unusual attributes containing JavaScript://, javascript:, onload=, onerror=, or script tags within shortcode parameters. Manually review the raw post_content for encoded or obfuscated payloads.
    Affected if Shortcode content contains unsanitized user input that could be interpreted as malicious JavaScript when rendered.

A user is affected if the Olevmedia Shortcodes plugin version 1.1.9 or lower is installed and active, and any content using the plugin's shortcodes exists in the database with unsanitized input that could execute as JavaScript.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 1.1.9
Interim mitigation

Update Olevmedia Shortcodes plugin to version greater than 1.1.9; if no patched version available, disable the plugin until a fix is released, or manually add input sanitization and output encoding to plugin code.

Fix this in Olevmedia Shortcodes Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25798 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-25798 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data