Skip to main content

 Security

Security guidance and advisories for PageSeeder

CVE-2024-4367

PDF.js: Arbitrary JavaScript execution through malicious PDF fonts

Published2024-05-14
Last updated2026-11-16
ComponentPDF.js
SeverityHigh
PageSeeder statusNot affected

Summary

Missing type validation in PDF.js font processing can allow a malicious PDF to execute attacker-controlled JavaScript in the hosting application origin.

The upstream advisory lists pdfjs-dist through 4.1.392 as affected. The issue is fixed in 4.2.67.

The upstream advisory rates the issue High.

For technical details, see the upstream security advisory .

PageSeeder impact assessment

Affected dependencyAffected PDF.js version in 6.0000–6.1000; fixed PDF.js version from 6.1001.
PageSeeder versions assessedPageSeeder 6.0000 through 6.3004
Vulnerability statusAffected in 6.0000–6.1000; Not affected from 6.1001
Conditions required for exploitationAn affected PDF.js version must open a crafted PDF while isEvalSupported is true, the vulnerable versions' default.
Relevant PageSeeder configurationPageSeeder 6.0000–6.1000 ship an affected PDF.js version (through 4.1.392). PageSeeder 6.1001 onward ship a fixed PDF.js version. PageSeeder 6.3004 ships PDF.js 6.5.438, which is newer than the fixed version 4.2.67.
Assessment date2026-11-13

Assessment

PageSeeder 6.0000–6.1000 are affected. Opening a crafted PDF in these releases presents the vulnerable viewer code path.

PageSeeder 6.1001 onward ship a fixed PDF.js version and are not affected.

PageSeeder 6.3004 is not affected because the shipped PDF.js version includes the upstream fix.

The version was checked inside the shipped module rather than inferred solely from the npm dependency declaration. No configuration workaround is required for this CVE in fixed versions.

This assessment applies to PageSeeder 6.0000 through 6.3004 in the reviewed standard configuration and matching frontend assets. Custom templates, independently replaced components and additional editor integrations may change exposure.

Evidence is based on source and shipped-asset review on 13 November 2026, with targeted jsdom tests where described. It does not establish the configuration of every deployed server or demonstrate a real-browser exploit.

Recommended action

Upgrade installations running PageSeeder 6.0000–6.1000

Installations running PageSeeder versions 6.0000 through 6.1000 should upgrade to PageSeeder 6.1001 or later to receive the fixed PDF.js version.

No CVE-specific action is required for PageSeeder 6.1001 onward.

References

Created on , last edited on