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

CVE-2026-8882

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-09
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 WP ApplicantStack Jobs Display plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Shortcode Attributes in all versions up to, and including, 1.1.1 due to insufficient input sanitization and output escaping. 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 WP ApplicantStack Jobs Display WordPress plugin up to version 1.1.1 is vulnerable to stored XSS via shortcode attributes due to missing input sanitization and output escaping. Authenticated attackers with contributor-level permissions can inject malicious JavaScript through shortcode parameters that executes when other users view affected pages.

MitigationUpdate the plugin to version 1.1.2 or later, which should include proper sanitization (such as sanitize_text_field or wp_kses) for shortcode attributes and output escaping (esc_attr, esc_html) when rendering those values.

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. Identify plugin installation status
    Navigate to WordPress admin > Plugins and locate 'WP ApplicantStack Jobs Display', or check the plugin directory /wp-content/plugins/ for the applicantstack-jobs-display folder
    Affected if The plugin is installed and active in WordPress
  2. Determine installed plugin version
    In WordPress admin > Plugins, click on the plugin name to view version details, or read the main plugin PHP file (e.g., applicantstack-jobs-display.php) and look for the 'Version' header in the plugin comment block
    Affected if Version is 1.1.1 or lower (any version up to and including 1.1.1)
  3. Check for contributor-level or higher user accounts
    In WordPress admin > Users, review the list of registered users and their assigned roles
    Affected if There are any user accounts with Contributor, Author, Editor, or Administrator roles present on the site
  4. Inspect pages and posts for shortcode usage
    Search the WordPress database or use a plugin to find instances of the shortcode [applicantstack_jobs] or [applicantstack-jobs-display] in posts, pages, and custom post types
    Affected if Any pages or posts contain the plugin shortcode, as this provides the injection vector
  5. Review shortcode attributes in database
    Examine the stored shortcode attributes in the wp_posts table or via page source to see if any contain unusual characters like <script>, javascript:, or event handlers such as onmouseover
    Affected if Shortcode attributes contain unsanitized HTML or JavaScript code that could execute when viewed

A user is affected if the plugin is installed at version 1.1.1 or lower AND any authenticated contributor-level user exists on the site AND pages containing the plugin shortcode are published.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.1.2 or later, which should include proper sanitization (such as sanitize_text_field or wp_kses) for shortcode attributes and output escaping (esc_attr, esc_html) when rendering those values.

Recommended fix Moderate confidence

Latest version after 1.1.1 from wordpress.org plugin repository

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'WP ApplicantStack Jobs Display' in the plugin list
  4. Check if an update is available and update to the latest version
  5. If no update is available via WordPress, download the latest version from the WordPress plugin repository at https://wordpress.org/plugins/applicantstack-jobs-display/
  6. Deactivate and delete the old version, then upload and activate the new version
  7. Verify the fix by testing shortcode functionality with typical input

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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