dbcve.org
PdfreactorFramework / library · Realobjects

CVE-2019-12153

CRITICAL · 10.0 CVSS v3.0 Published 2019-06-11
Fix available
A fix is available. Upgrade to 10.1.10722 or later.
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
Lack of validation in the HTML parser in RealObjects PDFreactor before 10.1.10722 leads to SSRF, allowing attackers to access network or file resources on behalf of the server by supplying malicious HTML content.

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

The HTML parser in RealObjects PDFreactor before version 10.1.10722 lacks proper validation, enabling Server-Side Request Forgery (SSRF). Attackers can supply malicious HTML content to trick the server into making unauthorized network requests or accessing local file resources.

MitigationUpgrade PDFreactor to version 10.1.10722 or later. Additionally, implement network segmentation and restrict outbound connections from the server to limit the impact of potential SSRF exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PdfreactorFramework / library
Affected:< 10.1.10722

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

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 PDFreactor version
    Locate the PDFreactor installation and check the version. This is typically found in the product documentation, license file, or by querying the service if running as a daemon. Common locations include the installation directory or within the application metadata.
    Affected if The installed version is below 10.1.10722 or cannot be determined (treat unknown versions as potentially vulnerable).
  2. Determine if HTML parsing is enabled
    Review your PDFreactor configuration to verify if the HTML-to-PDF conversion feature is in use. This is the primary attack surface for this SSRF vulnerability.
    Affected if HTML parsing functionality is actively used or available in your deployment.
  3. Check for network exposure
    Examine whether the PDFreactor service has network access or is configured to process HTML from untrusted sources such as user-provided content, external URLs, or data from client requests.
    Affected if The service can process HTML from external or untrusted sources and has network connectivity.

You are affected if your PDFreactor version is below 10.1.10722 and the HTML parsing feature is enabled with access to external content or network resources.

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.

dbcve · scoped
Upgrade available Upgrade to 10.1.10722 or later
Fixed in 10.1.10722
Interim mitigation

Upgrade PDFreactor to version 10.1.10722 or later. Additionally, implement network segmentation and restrict outbound connections from the server to limit the impact of potential SSRF exploitation.

Recommended fix High confidence

Pdfreactor version 10.1.10722 or later

  1. 1. Identify the current Pdfreactor version in use by checking the application or service documentation
  2. 2. Download the latest Pdfreactor version 10.1.10722 or later from the official vendor website (www.pdfreactor.com)
  3. 3. Review the upgrade instructions provided in the Pdfreactor release notes
  4. 4. Perform the upgrade following the vendor's recommended procedure
  5. 5. Verify the upgrade was successful by checking the Pdfreactor version information
  6. 6. Test that the HTML parsing functionality works correctly with the updated version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pdfreactor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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