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

CVE-2026-48880

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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
Subscriber Cross Site Scripting (XSS) in WP Job Portal <= 2.5.2 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 · moderate confidence

Stored Cross Site Scripting (XSS) vulnerability in WP Job Portal WordPress plugin affecting versions up to and including 2.5.2. Authenticated users with Subscriber role can inject malicious JavaScript code through plugin input fields, which is then stored and executed when other users view the injected content.

MitigationUpdate WP Job Portal to the latest version beyond 2.5.2; implement proper input sanitization and output encoding on all user-supplied data fields within the plugin.

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

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

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. Check WP Job Portal plugin version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins > WP Job Portal and view the version number displayed under the plugin name
    Affected if The installed version is 2.5.2 or lower (any version up to and including 2.5.2)
  2. Verify WordPress user roles with Subscriber access
    Go to Users > All Users in WordPress admin and check if any users have the Subscriber role assigned
    Affected if At least one user with Subscriber role exists in the system
  3. Inspect plugin-generated pages for stored XSS
    View source code of pages rendered by WP Job Portal (job listings, application forms, user profiles) and search for unsanitized script tags or event handlers in HTML output
    Affected if JavaScript code appears unescaped in HTML source (e.g., <script>, onload=, onerror=, javascript:)
  4. Check browser developer console for XSS alerts
    As a logged-in user (different from the Subscriber account), navigate to WP Job Portal pages and open browser console to observe if any script execution or errors occur
    Affected if JavaScript executes or console shows XSS-related errors when viewing plugin pages

A user is affected if WP Job Portal version is 2.5.2 or lower AND any Subscriber-level user account exists in WordPress, allowing stored XSS to be injected into plugin input fields.

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 WP Job Portal to the latest version beyond 2.5.2; implement proper input sanitization and output encoding on all user-supplied data fields within the plugin.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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