dbcve.org
CWE-403Weakness · CWE-403

CVE-2026-40042

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Pachno 1.0.6 contains an XML external entity injection vulnerability that allows unauthenticated attackers to read arbitrary files by exploiting unsafe XML parsing in the TextParser helper. Attackers can inject malicious XML entities through wiki table syntax and inline tags in issue descriptions, comments, and wiki articles to trigger entity resolution via simplexml_load_string() without LIBXML_NONET restrictions.

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

Pachno 1.0.6 is vulnerable to XML external entity (XXE) injection through the TextParser helper, which uses simplexml_load_string() without the LIBXML_NONET restriction. Unauthenticated attackers can inject malicious XML entities via wiki table syntax and inline tags in issue descriptions, comments, and wiki articles, allowing them to read arbitrary files from the server filesystem.

MitigationApply the LIBXML_NONET flag to all simplexml_load_string() calls in the TextParser and related XML parsing code to prevent external entity resolution, and implement input validation to sanitize or reject potentially malicious XML constructs.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify installed Pachno version
    Locate the version file or admin panel in your Pachno installation (typically in a VERSION file or accessible via the web interface under admin/settings). Compare this version to 1.0.6.
    Affected if The installed version is 1.0.6 or if the TextParser helper has not been patched to include LIBXML_NONET.
  2. Locate the TextParser helper file
    Search your Pachno source code for files containing the TextParser class or the simplexml_load_string() function call. This is typically found in a helper or parser-related PHP file.
    Affected if The TextParser file contains simplexml_load_string() calls without the LIBXML_NONET flag.
  3. Inspect XML parsing code for LIBXML_NONET flag
    Open the identified TextParser file and search for simplexml_load_string(). Verify whether the function call includes LIBXML_NONET as the second argument (e.g., simplexml_load_string($xml, 'SimpleXMLElement', 0, LIBXML_NONET)).
    Affected if simplexml_load_string() is called without the LIBXML_NONET flag, leaving the parser vulnerable to external entity resolution.
  4. Confirm wiki and comment features are accessible
    Check whether the wiki, issue descriptions, and comments features are enabled in your Pachno installation. These are typically accessible via the web interface to authenticated users (and potentially unauthenticated users depending on configuration).
    Affected if Users can submit or edit content in issue descriptions, comments, or wiki articles that accept the vulnerable wiki table syntax or inline tags.
  5. Verify external entity resolution is possible
    Attempt to submit a test XML payload with an external entity reference (e.g., <!DOCTYPE test [<!ENTITY xxe SYSTEM "file:///etc/hostname">]><test>&xxe;</test>) in a wiki table or inline tag within an issue description or comment. Observe whether the external entity is resolved and the content is rendered.
    Affected if The submitted XML entity is resolved and the content from the external source (or local file) is displayed in the output, confirming the XXE vulnerability is exploitable.

You are affected if your Pachno installation is version 1.0.6 (or uses an unpatched TextParser) AND the TextParser uses simplexml_load_string() without the LIBXML_NONET flag, allowing XML external entities to be resolved when processing wiki table syntax or inline tags in issue descriptions, comments, or wiki articles.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the LIBXML_NONET flag to all simplexml_load_string() calls in the TextParser and related XML parsing code to prevent external entity resolution, and implement input validation to sanitize or reject potentially malicious XML constructs.

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

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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