Security readout for executives and security teams
Plain-English summary
PDF Signer 3.0 is reported to let an unauthenticated internet attacker run code on the server through unsafe handling of a cookie value. A successful attack could expose documents, credentials, and the host system. Public exploit material is referenced, but the provided sources do not show confirmed active exploitation or a vendor patch.
Executive priority
Treat this as urgent if PDF Signer 3.0 is in use, because the reported impact is full unauthenticated remote code execution. If no deployment exists, document non-exposure and monitor vendor or advisory updates.
Technical view
The CVE describes server-side template injection in PDF Signer 3.0 through the CSRF-TOKEN cookie, leading to arbitrary code execution without authentication. CVSS is 9.8 critical with network attack vector and high confidentiality, integrity, and availability impact. The source bundle lists CWE-352, though the described weakness is template injection behavior.
Likely exposure
Exposure is likely limited to organizations running simcy_creative PDF Signer version 3.0, especially if reachable from the internet. The provided sources do not identify other affected versions, hosted variants, or downstream products.
Exploitation context
ExploitDB is listed as a public exploit reference, so defenders should assume exploit knowledge is available. The bundle does not cite CISA KEV listing or confirmed in-the-wild exploitation, so active exploitation is unproven from these sources.
Researcher notes
Evidence supports critical impact and public exploit availability, but patch status and exploitation-in-the-wild evidence are incomplete in the provided bundle. The CWE mapping may be imprecise relative to the described server-side template injection path.
Mitigation direction
- Identify and prioritize all PDF Signer 3.0 deployments.
- Check vendor and VulnCheck guidance for patched versions or official remediation.
- Restrict internet access to affected instances until remediation is confirmed.
- Retire or isolate unsupported PDF Signer 3.0 systems.
- Review logs for suspicious CSRF-TOKEN cookie values and unexpected server execution.
Validation and detection
- Inventory web assets for PDF Signer 3.0 installations.
- Confirm product version from application files, admin UI, or deployment records.
- Review web logs for abnormal CSRF-TOKEN cookie values.
- Check host telemetry for unexpected child processes from the web server.
- Verify whether vendor guidance identifies a fixed release.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2019-25729 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-46276CVE reference, VulnCheck · exploit
- Official Product HomepageCVE reference, VulnCheck · product
- Product ReferenceCVE reference, VulnCheck · product
- VulnCheck Advisory: PDF Signer 3.0 Server-Side Template Injection RCE via CSRF CookieCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery
Cross-Site Request Forgery represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.