Simple Job BoardWordPress extension · Presstigers
CVE-2017-18498
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 · uneditedThe simple-job-board plugin before 2.4.4 for WordPress has reflected XSS via keyword search.
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 confidenceThe simple-job-board WordPress plugin before version 2.4.4 contains a reflected cross-site scripting (XSS) vulnerability in the keyword search functionality. User-supplied input in the search parameter is not properly sanitized or escaped before being reflected back in the page output, allowing an attacker to inject malicious JavaScript code that executes in the victim's browser.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Simple Job BoardWordPress extension
< 2.4.4CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Simple Job Board plugin is installedNavigate to WordPress admin > Plugins and locate 'Simple Job Board' by Presstigers in the installed plugins listAffected if The plugin is not present in the plugin list
-
Identify the installed plugin versionIn the Plugins list, click on the plugin to view its details, or inspect the plugin header comment in /wp-content/plugins/simple-job-board/ or /wp-content/plugins/simple-job-board/index.php to find the Version: X.X.X entryAffected if The displayed version number is less than 2.4.4 (for example, 2.4.3, 2.4.0, 2.3.0, etc.)
-
Locate the job board search pageVisit the frontend page where the job board search form is displayed (typically a page with the [simple_job_board] shortcode or a job listing page with a keyword search input field)Affected if No job board search page exists or the search form is not present on the site
-
Verify the search parameter reflects input without encodingEnter a test string such as <script>alert(1)</script> into the keyword search field and submit. Inspect the page source or observe whether the raw script tags appear in the HTML output without being converted to HTML entitiesAffected if The submitted test string is reflected verbatim in the HTML output (the script tags are visible in the page source rather than being encoded as <script>)
You are affected if the Simple Job Board plugin version is below 2.4.4 AND the job search page exists and reflects unsanitized user input from the search parameter in the page output.
Generated from the published advisory. Verify against your own configuration.
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 data2.4.4
Update the simple-job-board plugin to version 2.4.4 or later, which includes proper input sanitization and output encoding for the search parameter.
Fix this in Simple Job Board
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18498 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-18498 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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