CVE Intelligence
Analysis AI-assisted

CVE-2026-25377: eyecix Addon Jobsearch Chat - SQL Injection

CVE-2026-25377 is a SQL injection weakness (CWE-89) in the eyecix Addon Jobsearch Chat WordPress addon, as described in the record. The CNA rated it critical with a CVSS 3.1 base score of 9.3, and the description places affected versions at n/a through 3.0 inclusive. The record lists no fixed version and no confirmed exploitation in the sources consulted.

Published Oct 13, 2026 · Updated Oct 13, 2026 · Ler em português

Overview

CVE-2026-25377 is a SQL injection weakness (CWE-89) in the Addon Jobsearch Chat addon (package addon-jobsearch-chat) published by eyecix for WordPress. According to the record, special characters used in an SQL command are not properly neutralized, which can allow crafted input to alter database queries.

Impact

  • The CNA (audit@patchstack.com) assigned a CVSS 3.1 base score of 9.3 with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L.
  • Decoded from the vector, the flaw is network-reachable, has low attack complexity, requires no privileges or user interaction, changes scope, and has high confidentiality impact, no integrity impact and low availability impact.
  • The practical consequences in a specific installation depend on the database account and data exposed; the record does not describe them further.

Affected products and versions

  • The description states the issue affects Addon Jobsearch Chat from n/a through 3.0 inclusive (<= 3.0).
  • The structured affected-product list in the record is empty, so no machine-readable version ranges are available.
  • Sites running this addon should treat any version in the stated range as potentially affected until the vendor or Patchstack confirms otherwise.

Exploitation status

  • The CISA KEV catalog does not list this CVE in the record, so no active exploitation is recorded there.
  • No confirmed exploitation in the wild appears in the sources consulted for this analysis.
  • The EPSS probability is 0.00283 (percentile 0.19274), a statistical estimate of exploitation likelihood rather than evidence of attacks.

Remediation and mitigation

  • The record contains no fixed version. This does not mean no fix exists; check the plugin vendor and the Patchstack entry for an updated release.
  • Until a fix is confirmed, consider disabling the addon if it is not essential, and restrict access to its functions where possible.
  • Apply the principle of least privilege to the WordPress database account so that a compromised query path has limited reach.
  • Place a web application firewall or equivalent filtering in front of the site as a compensating control, recognising that it reduces but does not remove risk.
  • Keep WordPress core, other plugins and themes updated, and review the Patchstack advisory for vendor-specific details.

Detection guidance

  • Review web server and application logs for unusual or malformed values submitted to the addon's chat and job search functions.
  • Watch for database error messages surfaced in web responses, which can indicate that input reaches SQL queries unfiltered.
  • Monitor the database for queries or access patterns that do not match normal plugin behaviour.
  • Verify the installed addon version against the stated range and maintain an inventory of WordPress plugins.

Limitations of the available information

  • The record has no title in the structured field and no affected or fixed version list.
  • The CVSS score comes from the CNA; no separate NVD or other scoring provider entry appears in the record.
  • The record lists a source status of Deferred, so details may change as the CVE is processed.
  • The EPSS date in the record (2026-10-13) should be verified against the source before relying on that score's timing.
  • Full exploit conditions and the exact vulnerable code path are not described in the available data.

Frequently asked questions

Is CVE-2026-25377 being actively exploited?

The CISA KEV catalog does not list it in this record, and no confirmed exploitation in the wild appears in the sources consulted.

Which versions are affected?

The description states versions from n/a through 3.0 inclusive. The record has no structured affected list and no fixed version.

What should site owners do now?

Check the vendor and Patchstack entry for an update, consider disabling the addon if it is not essential, and limit database privileges and exposure.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.