Atomic Edge analysis of CVE-2026-118068: A stored DOM-based cross-site scripting flaw in JobBoardWP versions up to and including 1.3.6. The vulnerability lives in the [jb_jobs] shortcode attribute handling, where the ‘no-jobs-text’ and related text attributes are passed through to the frontend without sanitization. A secondary entry point exists via the ‘job_description’ parameter in the front-end submission handler, which the patch also hardens by stripping shortcodes. Atomic Edge rates this as CVSS 6.4 (medium), but the public auto-provisioning of jb_employer accounts means the practical barrier is low.
Root cause: In jobboardwp/includes/frontend/class-shortcodes.php, the jb_jobs shortcode accepted the ‘no-jobs-text’, ‘no-jobs-search-text’, and ‘load-more-text’ attributes without sanitization. Before the patch, these values flowed directly into the rendered shortcode output. When the value is a shortcode fragment such as [jb_job id='” onmouseover=alert(1) x=”‘], it is later expanded by do_shortcode inside a DOM sink, producing stored DOM XSS. The patch adds a foreach loop (lines 494-532) that applies sanitize_text_field() to the three text attributes, plus absint() to numeric attributes and sanitize_key() to ‘orderby’. Separately, jobboardwp/includes/frontend/class-actions-listener.php line 538 was changed from wp_kses_post( wp_unslash( $_POST[‘job_description’] ) ) to wp_kses_post( strip_shortcodes( wp_unslash( $_POST[‘job_description’] ) ) ). The strip_shortcodes call is what closes the shortcode-injection route into the [jb_jobs] renderer. The single job shortcode also gained absint() on $atts[‘id’] at line 416, and the jobs dashboard shortcode gained column key/value sanitization at lines 579-585.
Exploitation: An attacker registers through the default public submission workflow, which auto-provisions a jb_employer account. They then submit a job whose job_description contains a shortcode such as [jb_jobs no-jobs-text=”” onmouseover=alert(document.cookie) x=””]. On a page displaying the jb_jobs shortcode with no matching results, the attacker-controlled attribute is rendered into the no-jobs message container. The resulting DOM mutation executes arbitrary JavaScript in the browser of any visitor who views the page carrying the shortcode. No WordPress nonce or admin interaction is required, only the ability to contribute content through the standard submission form at the job posting endpoint.
Patch Analysis: Version 1.3.7 addresses the flaw at three layers. First, class-shortcodes.php now type-casts and sanitizes every jb_jobs attribute before use, so text attributes cannot carry shortcode syntax or angle brackets. Second, class-actions-listener.php calls strip_shortcodes() on job_description before wp_kses_post(), preventing attacker shortcodes from being persisted into the post content. Third, the jobs dashboard shortcode sanitizes column keys and values, and the single job shortcode casts id to int. The plugin version in jobboardwp.php was bumped from 1.3.6 to 1.3.7. Together these changes remove the shortcode-expansion path that turned benign-looking submission data into executable DOM content.
Impact: Successful exploitation yields stored DOM XSS in any page rendering the affected shortcode. An attacker can steal administrator session cookies, perform authenticated actions as a logged-in admin, inject persistent malicious scripts into job listings viewed by recruiters and applicants, and pivot to full site compromise through theme or plugin editors. Because the public submission flow creates the account automatically, a stock install is effectively exposed to unauthenticated attackers despite the ‘Authenticated (Custom+)’ label.







