/

CVE-2026-94039

Severity:

HIGH RISK

(7.3)

SSRF (CWE-918) in TaxHacker Invoice PDF Renderer Component

CVE-2026-94039

Deferred

Vulnerability type

Category:

Server-Side Request Forgery

CWE:

CWE-918

Impact:

Unauthorized server-side network access and potential internal resource disclosure

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A server-side request forgery vulnerability in TaxHacker's Invoice PDF Renderer allows a remotely supplied businessLogo value to influence server-side network requests. When the renderer processes an attacker-controlled logo reference, the server may request internal or otherwise unintended resources.

Affected context

The issue occurs in the generateInvoicePDF function within

/apps/invoices/actions.ts when the Invoice PDF Renderer processes the

businessLogo argument. Deployments may be exposed when this value can be

influenced remotely and the server has network access to internal services,

cloud metadata endpoints, or other protected destinations.

Exploit preconditions

  • Attack surface: Remote invoice PDF generation functionality
  • Required access: Ability to submit or influence the businessLogo argument
  • Trigger point: Server-side processing of the logo while generating an invoice PDF
  • Why exploitation is possible: The application may retrieve attacker-influenced resources from the server without sufficiently restricting destination URLs or network targets

Why this happens

The vulnerability results from treating a user-controlled resource reference as

an acceptable destination for a server-side request. Without strict validation,

destination allowlisting, and network-level restrictions, the PDF renderer may

access resources that the requesting user could not reach directly. This behavior

maps to CWE-918: Server-Side Request Forgery.

Potential impact

  • An attacker may cause requests to internal services
  • Sensitive responses or service metadata could be disclosed
  • Cloud instance metadata or credential material could be exposed where reachable
  • Internal network services may be probed or abused
  • The server's network position could enable further lateral movement

General mitigation guidance

Mitigation generally focuses on reducing trust in externally supplied resource

locations and constraining outbound connectivity.

Common defensive patterns include:

  • Accepting only approved image sources or using server-managed asset identifiers
  • Enforcing strict URL parsing and destination allowlists
  • Blocking loopback, link-local, private, reserved, and otherwise sensitive address ranges
  • Revalidating destinations after DNS resolution and redirect processing
  • Restricting outbound network access from the rendering service
  • Running the renderer with least-privilege network and filesystem permissions
  • Applying request timeouts, response-size limits, and safe redirect policies

How teams detect issues like this

Detection approaches may include:

  • Static analysis for network requests built from user-controlled URL or path values
  • Code review of PDF, image, preview, and document-rendering features
  • Tests covering private-address, loopback, link-local, redirect, and DNS-rebinding cases
  • Egress monitoring for unexpected requests from the invoice rendering service
  • Network policies that alert on or deny access to protected address ranges
  • Application logging that records normalized destinations and request outcomes without exposing sensitive response data

Automated security review tools can help identify user-controlled values reaching

server-side HTTP clients, but findings should be validated against deployment

network controls.

Sources

SourceLink
github.comgithub.com/vas3k/TaxHacker/
github.comgithub.com/vas3k/TaxHacker/issues/186
vuldb.comvuldb.com/cve/CVE-2026-94039
vuldb.comvuldb.com/submit/947878
vuldb.comvuldb.com/vuln/407968
vuldb.comvuldb.com/vuln/407968/cti

Frequently asked

questions

Yes. Exploitation may be possible remotely when an attacker can influence the

businessLogo value used during invoice PDF generation.

Not necessarily. The server performs the request, so the attacker may only need

access to the exposed invoice-generation functionality. The server's reachable

network resources determine the practical impact.

Avoid fetching arbitrary user-supplied destinations. Prefer server-managed assets

or strict source allowlists, combined with outbound network restrictions and

protections against redirects and DNS-based bypasses.

Treat externally supplied URLs as untrusted, review all server-side fetches,

test private and reserved address handling, and enforce egress policies around

services that process remote resources.

Find out what's already
exploitable in your codebase.