CVE-2026-25376
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in eyecix Addon Jobsearch Chat addon-jobsearch-chat allows Reflected XSS.This issue affects Addon Jobsearch Chat: from n/a through <= 3.0.
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 · moderate confidenceReflected XSS vulnerability in the eyecix Jobsearch Chat addon allows attackers to inject malicious scripts via unsanitized user input that gets reflected back in web pages. The CVSS 7.1 score indicates the vulnerability is exploitable but requires user interaction (e.g., clicking a crafted link).
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if eyecix Jobsearch Chat addon is installedCheck your CMS/plugin directory for the eyecix Jobsearch Chat addon files, or check the plugin/component list in your CMS admin panel for a component named Jobsearch ChatAffected if The addon is present in the environment
-
Determine the installed versionLocate the version information in the addon's manifest file, changelog, version metadata, or composer.json. Compare your version to any affected version ranges if knownAffected if The installed version has known vulnerable releases or falls within an affected version range
-
Inspect chat input handling codeReview the addon source code for how user input flows through the application. Look for code that takes parameters from HTTP requests and reflects them directly into HTML output without processingAffected if User input is reflected in web pages without sanitization routines present in the code
-
Check for output encoding on reflected dataExamine how data is rendered in HTML responses. Verify if context-aware encoding functions (like htmlspecialchars) are used before displaying any user-supplied valuesAffected if User-supplied data appears in responses without encoding/escaping applied
-
Identify accessible input vectorsMap all user-controllable inputs in the chat addon: form fields, URL parameters, AJAX endpoints. Determine which ones can be reflected in page outputAffected if Any user input field can be reflected in the page output without validation
The environment is affected if the eyecix Jobsearch Chat addon is installed and user input is reflected in web pages without proper sanitization and output encoding.
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 dataImplement proper input validation and output encoding/escaping for all user-supplied data before rendering in HTML context. The fix involves identifying all input vectors in the addon and applying context-aware sanitization.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25376 — 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-2026-25376 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