medium · CVSS v3 4.3

CVE-2026-17167

IBM API Connect 12.1.0.0 through 12.1.1.2 can allow an authenticated attacker to falsify audit logs by supplying crafted input. This undermi

Overview

IBM API Connect 12.1.0.0 through 12.1.1.2 can allow an authenticated attacker to falsify audit logs by supplying crafted input. This undermines the integrity of audit trails used for compliance and incident response. The vulnerability does not affect availability or confidentiality of data directly.

Description

IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to falsify audit log information due to reliance on untrusted inputs. Information supplied by the client is relied on when recording the source of a request, so audit records could contain inaccurate details.

Impact

Confidentiality: audit logs may contain false information, potentially misleading investigations. Integrity: the audit trail is compromised, eroding trust in logged events. Availability: not directly impacted. Defenders: security teams, compliance auditors, incident responders.

Remediation

Apply the IBM security patch for CVE-2026-17167 from IBM Fix Central. If immediate patching is not possible, restrict administrative access to API Connect, enforce strict input validation on request source fields, and monitor audit logs for anomalies. Consider disabling audit logging of request source until the patch is applied.

Risk context

The vulnerability has a medium CVSS v3 score of 4.3 and no EPSS data, indicating moderate risk. Prompt patching is recommended to preserve audit integrity.

Affected products

  • IBM API Connect 12.1.0.0
  • IBM API Connect 12.1.1.0
  • IBM API Connect 12.1.1.1
  • IBM API Connect 12.1.1.2

Scores

Severity
medium
CVSS v2
4
CVSS v3
4.3
CVSS v4
—
EPSS
—

audit-falsification IBM API-Connect medium authenticated log-integrity compliance

← All CVEs

Related CVEs

medium

CVE-2026-118528

The Directorist: AI-Powered Business Directory, Listings & Classified Ads WordPress plugin before 8.11 does not validate that the requesting user owns the referenced listing before returning its metadata via an AJAX action, allowing authenticated attackers with Subscriber-level access and above to disclose another user's private and unpublished draft listing details, including contact information.

View analysis

medium

CVE-2026-118204

The WP Data Access – App Builder plugin for WordPress is vulnerable to stored XSS via the ImageURL column value. Authenticated users with subscriber-level access can inject scripts that run when others view the page. This flaw allows malicious code to execute in the context of site visitors.

View analysis

medium

CVE-2026-121792

The GamiPress – Gamification plugin to reward points, badges & ranks in WordPress, now with AI plugin for WordPress is vulnerable to generic SQL Injection via the 'input_ . (Gravity Forms name-field part, or list-field row)' parameter in all versions up to, and including, 8.1.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation requires a GamiPress achievement already configured against a Gravity Forms 'field value submission' event with the corresponding form published — a standard setup for sites using the integration.

View analysis

medium

CVE-2026-93902

The Soledad theme for WordPress is vulnerable to Stored Cross-Site Scripting via Social Profile Fields in all versions up to, and including, 8.7.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected payload is scoped to the attacker's own user meta but is exposed publicly on their author archive page at /author/ /, which is accessible to unauthenticated visitors regardless of whether the attacker has published any posts.

View analysis