dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-1899

MEDIUM · 6.4 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The Any Post Slider plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's aps_slider shortcode in all versions up to, and including, 1.0.4 due to insufficient input sanitization and output escaping on the 'post_type' attribute. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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

The Any Post Slider WordPress plugin (versions up to 1.0.4) suffers from a stored XSS vulnerability in the aps_slider shortcode. The post_type parameter is not properly sanitized on input or escaped on output, allowing authenticated contributors and above to inject malicious JavaScript that executes when pages containing the shortcode are accessed.

MitigationUpdate the plugin to version 1.0.5 or later if available; otherwise, implement proper input sanitization (sanitize_text_field) and output escaping (esc_attr) on the post_type attribute in the shortcode handler.

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

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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 is installed and get version
    Access WordPress admin > Plugins, find 'Any Post Slider' and note the installed version number
    Affected if Plugin version is 1.0.4 or lower (versions up to 1.0.4 are affected)
  2. Confirm version is vulnerable
    Compare installed version against the affected range: versions up to 1.0.4 are vulnerable
    Affected if Version is 1.0.4 or any version lower than 1.0.4
  3. Identify shortcode usage in content
    Search WordPress posts, pages, and custom post types for the '[aps_slider' shortcode using database query or plugin scanner
    Affected if The aps_slider shortcode is present in any published content
  4. Inspect shortcode for post_type parameter
    Examine the shortcode usage to see if post_type attribute is present, for example: [aps_slider post_type="..."]
    Affected if The shortcode includes a post_type parameter with unsanitized user-controlled value

You are affected if the Any Post Slider plugin version is 1.0.4 or lower AND the aps_slider shortcode with a post_type parameter is in use on your site, allowing stored XSS execution.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.0.5 or later if available; otherwise, implement proper input sanitization (sanitize_text_field) and output escaping (esc_attr) on the post_type attribute in the shortcode handler.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1899 — 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-2026-1899 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