CVE-2026-25377
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 Special Elements used in an SQL Command ('SQL Injection') vulnerability in eyecix Addon Jobsearch Chat addon-jobsearch-chat allows SQL Injection.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 confidenceSQL Injection vulnerability in eyecix Addon Jobsearch Chat allows attackers to inject malicious SQL commands via unsanitized input in the plugin's database queries, potentially enabling unauthorized data access, modification, or deletion.
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
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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 the eyecix Addon Jobsearch Chat pluginCheck your WordPress plugins directory or plugin admin panel for a plugin named 'eyecix Addon Jobsearch Chat' or 'Jobsearch Chat' by eyecixAffected if the plugin is installed and active
-
Determine the installed plugin versionView the plugin details in WordPress admin under Plugins, or check the plugin's main PHP file for a version comment or constantAffected if the version cannot be determined or is unknown
-
Locate the jobsearch chat database interaction codeSearch the plugin files for SQL query functions (such as $wpdb->prepare, mysqli_query, or raw SQL execution) related to chat functionality, typically in files named 'chat.php', 'jobsearch-chat.php', or similar within the plugin folderAffected if direct SQL queries exist without $wpdb->prepare or parameterized statements
-
Inspect user input handling in chat queriesReview the identified SQL query code to determine if $_GET, $_POST, or $_REQUEST parameters are used directly in queries without sanitization or parameter bindingAffected if user-supplied input from request parameters is concatenated directly into SQL queries without escaping or prepared statements
-
Test for SQL injection vulnerabilityIf you have a staging environment, use a SQL injection testing tool or manually inject a single quote and SQL meta-characters into chat-related URL parameters (such as job_id, user_id, or chat_id) to observe database errorsAffected if the application returns SQL syntax errors or behaves unexpectedly with malicious input
A user is affected if the eyecix Addon Jobsearch Chat plugin is installed with user input being directly concatenated into SQL queries without prepared statements or proper sanitization.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements, implement proper input validation and sanitization on all user-supplied data before constructing database queries.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25377 — 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-25377 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