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

CVE-2026-57383

HIGH · 7.1 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 5 weeks old

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in eyecix JobSearch wp-jobsearch allows Stored XSS.This issue affects JobSearch: from n/a through <= 3.2.9.

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 confidence

Stored Cross-site Scripting (XSS) vulnerability in the JobSearch WordPress plugin allows authenticated attackers to inject malicious JavaScript through unsanitized input fields. The injected payload persists in the database and executes when other users (including administrators) view the affected pages, potentially enabling session hijacking, credential theft, or defacement.

MitigationUpgrade JobSearch plugin to a version beyond 3.2.9 that includes proper input sanitization and output encoding. Alternatively, implement a WAF rule to filter XSS payloads and manually audit all user input handling functions in the plugin code.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify JobSearch plugin installation and activation status
    In WordPress admin, go to Plugins > Installed Plugins and locate JobSearch plugin. Confirm it shows as 'Active'. Alternatively, check the /wp-content/plugins/ directory for the jobsearch folder and its presence in the wp_options table where option_name = 'active_plugins'.
    Affected if JobSearch plugin is installed and active on the WordPress site
  2. Identify installed JobSearch plugin version
    Navigate to Plugins > Installed Plugins > JobSearch. The version number is displayed below the plugin name. Alternatively, read the '/jobsearch/readme.txt' or 'jobsearch.php' file header for the 'Version' tag.
    Affected if Version is 3.2.9 or lower (the vulnerability exists up to and including 3.2.9)
  3. Confirm plugin features accepting user input are enabled
    Review JobSearch settings at JobSearch > Plugin Settings. Look for features such as job submissions, candidate applications, resume uploads, or any public-facing forms that accept user-submitted content. Check if these features are set to 'Enable' or are publicly accessible.
    Affected if Any JobSearch form accepting user input (job postings, applications, profiles) is enabled and publicly accessible to authenticated users
  4. Inspect database for suspicious script injections in JobSearch data
    Query the WordPress database (e.g., via phpMyAdmin or wp CLI): SELECT * FROM wp_postmeta WHERE meta_value LIKE '%<script%' OR meta_value LIKE '%onerror=%' OR meta_value LIKE '%onload=%'; Also check wp_posts and any custom JobSearch tables (e.g., wp_jobsearch_applications, wp_jobsearch_jobs) for encoded or obfuscated XSS patterns.
    Affected if Database records contain unsanitized HTML/script tags in JobSearch-related fields indicating prior exploitation

A site is affected if JobSearch plugin version 3.2.9 or lower is active with user input features enabled, or if suspicious script tags are found in JobSearch database tables.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade JobSearch plugin to a version beyond 3.2.9 that includes proper input sanitization and output encoding. Alternatively, implement a WAF rule to filter XSS payloads and manually audit all user input handling functions in the plugin code.

Recommended fix Moderate confidence

Latest version of JobSearch plugin (verify > 3.2.9 on WordPress repository or with vendor)

  1. Verify the current installed version of the JobSearch plugin in WordPress admin under Plugins
  2. Check WordPress plugin repository or contact eyecix for the latest security release beyond version 3.2.9
  3. Backup the WordPress site before performing any updates
  4. Update the JobSearch plugin to the latest available version
  5. Verify the update was successful and test that the plugin functionality works as expected
  6. Monitor for any security advisories related to this specific XSS vulnerability
Caveat Review changelog for any breaking changes between current version and the new version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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