Skip to main content
CVE-2026-118068VulnerabilityPublished

The JobBoardWP – Job Board Listings and Submissions plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-118068· Medium 6.4

Not known to be exploited · CVSS 6.4 Medium.

Data as of 18 Nov 2026, 17:05 UTC

CVSS 3.1 base score
6.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.16.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
ultimatememberJobBoardWP – Job Board Listings and SubmissionsAffected
  • <=1.3.6
Fixed in–

AI-suggested

Until a fix is available, administrators should consider disabling public submissions or restricting access to trusted users only to mitigate exploitation risk.

Description

The JobBoardWP plugin for WordPress versions up to and including 1.3.6 is affected by a Stored DOM-Based Cross-Site Scripting (XSS) vulnerability via the 'job_description' parameter. This vulnerability arises from insufficient input sanitization and output escaping, allowing authenticated attackers with custom-level access or higher to inject malicious scripts. Due to the plugin's default behavior of auto-provisioning a jb_employer account for any visitor, the effective attack entry point is unauthenticated, as the custom role requirement does not effectively restrict access on a default installation.

References

Community reviews

Loading reviews…