CVE-2026-8193
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 · uneditedA weakness has been identified in Akaunting 3.1.21. This issue affects some unknown processing of the file config/dompdf.php of the component Invoice PDF Rendering. Executing a manipulation can lead to server-side request forgery. The attack may be launched remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceA Server-Side Request Forgery (SSRF) vulnerability exists in Akaunting 3.1.21's Invoice PDF Rendering component, specifically in the config/dompdf.php file. The vulnerability allows remote attackers to make the server perform arbitrary requests to internal or external resources by manipulating input passed to the dompdf library, which is used for generating PDF invoices.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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.
-
Confirm Akaunting versionLocate the installed Akaunting version by checking the version file, composer.json, package.json, or the admin dashboard 'About' or 'System Info' page. Compare the version number to 3.1.21.Affected if The installed version is 3.1.21 exactly, or if the version cannot be determined but PDF invoice generation is available.
-
Verify Invoice PDF Rendering is accessibleDetermine if users can access the Invoice PDF export/download feature within Akaunting. Attempt to generate an invoice PDF or check if the route /invoices/{id}/pdf or similar is available.Affected if The Invoice PDF generation feature is enabled and accessible to users.
-
Inspect dompdf configuration fileLocate and examine the config/dompdf.php file in the Akaunting installation directory. Look for settings related to HTTP requests, remote fetching, or URL handling.Affected if The dompdf configuration file exists and contains settings that allow remote URL fetching (such as DOMPDF_ENABLE_REMOTE or similar options set to true).
-
Check for user-controlled input in invoice processingReview how invoice data is passed to the PDF renderer. Determine if any invoice fields (such as URL parameters, custom fields, or company details) can influence the dompdf configuration.Affected if User-supplied or invoice-specific data can be passed to or influence the PDF generation process without validation.
You are affected if running Akaunting version 3.1.21, the Invoice PDF Rendering feature is enabled, and the dompdf configuration allows remote content fetching.
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 dataImplement strict input validation and URL allowlist controls for any URLs processed by dompdf configuration. Additionally, restrict outbound network access from the application server and disable unnecessary URL fetching capabilities in dompdf. Consider upgrading to a patched version if available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8193 — 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-8193 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