dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-41143

HIGH · 8.8 CVSS v3.1 Published 2026-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
YesWiki is a wiki system written in PHP. Prior to version 4.6.1, YesWiki bazar module contains a SQL injection vulnerability in tools/bazar/services/EntryManager.php at line 704. The $data['id_fiche'] value (sourced from $_POST['id_fiche']) is concatenated directly into a raw SQL query without any sanitization or parameterization. This issue has been patched in version 4.6.1.

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

SQL injection vulnerability in YesWiki's bazar module where the id_fiche POST parameter is directly concatenated into an SQL query in tools/bazar/services/EntryManager.php at line 704 without sanitization or parameterization, allowing unauthenticated attackers to inject arbitrary SQL commands.

MitigationUpgrade to YesWiki version 4.6.1 or later which implements parameterized queries. If immediate upgrade is not feasible, apply input validation and parameterization to the vulnerable query in EntryManager.php line 704.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Confirm YesWiki installation and version
    Locate the YesWiki installation directory and check the version.php or changelog file. Common paths include the root directory or a 'yeswiki' subdirectory. Look for a version number in files like 'version.php', 'changes.md', or the wiki's about page.
    Affected if The installed YesWiki version is below 4.6.1 (the fixed version).
  2. Verify bazar module is enabled
    Check if the bazar module is present and active. Look for the 'tools/bazar' directory in the YesWiki installation. Check configuration files (often in 'tools/bazar' or the main configuration) to confirm bazar is not explicitly disabled.
    Affected if The bazar module is installed and enabled, making the vulnerable endpoint accessible.
  3. Locate the vulnerable file EntryManager.php
    Navigate to tools/bazar/services/EntryManager.php in the YesWiki installation directory. Open the file and locate around line 704 where the SQL query involving id_fiche is constructed.
    Affected if The file exists and contains SQL query code around line 704 that uses the id_fiche parameter.
  4. Inspect the vulnerable code for direct concatenation
    Examine the code around line 704 in EntryManager.php. Look for SQL query construction where $_POST['id_fiche'] or similar POST parameter is directly concatenated into the query string without using prepared statements, parameter binding, or sanitization functions.
    Affected if The code shows direct concatenation of the id_fiche POST parameter into the SQL query without parameterization or escaping.
  5. Verify unauthenticated access to bazar functionality
    Confirm that the bazar functionality handling id_fiche is accessible without authentication. Test by making a POST request to a bazar entry form or API endpoint that accepts the id_fiche parameter, without providing login credentials.
    Affected if The vulnerable endpoint accepts unauthenticated requests, allowing remote attackers to exploit the SQL injection.

You are affected if you run YesWiki version below 4.6.1 with the bazar module enabled and accessible, where EntryManager.php line 704 contains direct SQL concatenation of the id_fiche POST parameter.

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 to YesWiki version 4.6.1 or later which implements parameterized queries. If immediate upgrade is not feasible, apply input validation and parameterization to the vulnerable query in EntryManager.php line 704.

Recommended fix High confidence

4.6.1

  1. 1. Back up the current YesWiki installation and database before upgrading.
  2. 2. Download YesWiki version 4.6.1 or later from the official repository.
  3. 3. Replace the existing YesWiki files with the new version, preserving configuration and custom files.
  4. 4. Run any available database migration scripts if provided.
  5. 5. Verify the upgrade by checking that tools/bazar/services/EntryManager.php uses parameterized queries for the id_fiche parameter.
  6. 6. Test the bazar module functionality to confirm normal operation.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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 locally
dbcve dependency scanner

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