dbcve.org
Document On Line Submission And Approval SystemApplication · Infodoc

CVE-2023-37290

HIGH · 7.5 CVSS v3.1 Published 2023-07-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
InfoDoc Document On-line Submission and Approval System lacks sufficient restrictions on the available tags within its HTML to PDF conversion function, and allowing an unauthenticated attackers to load remote or local resources through HTML tags such as iframe. This vulnerability allows unauthenticated remote attackers to perform Server-Side Request Forgery (SSRF) attacks, gaining unauthorized access to arbitrary system files and uncovering the internal network topology.

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

InfoDoc Document On-line Submission and Approval System contains an SSRF vulnerability in its HTML-to-PDF conversion function due to insufficient restrictions on HTML tags. Unauthenticated attackers can inject malicious HTML tags such as iframe to force the server to make requests to internal resources, read local files, and map internal network topology.

MitigationImplement strict allowlist-based HTML sanitization in the PDF conversion module, disabling or stripping dangerous tags (iframe, img with src, link, script, etc.) and preventing loading of external/local resources.

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
Document On Line Submission And Approval SystemApplication
Affected:= 22547= 22567

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 the installed version of InfoDoc
    Locate the InfoDoc application installation directory and check the version information, typically found in the application metadata, about page, or version file. This may be accessible via the application's admin interface or in the installation files.
    Affected if The installed version is 22547 or 22567
  2. Locate the HTML-to-PDF conversion function
    Access the InfoDoc web interface and identify any feature that converts HTML documents to PDF. This is often found in document submission, approval workflow, or report generation modules.
    Affected if The HTML-to-PDF conversion feature exists and is accessible to users
  3. Test for lack of input sanitization
    Submit an HTML document containing an iframe tag with a source pointing to an internal URL (e.g., http://localhost or http://internal-ip) through the PDF conversion function. Observe whether the server attempts to fetch the internal resource.
    Affected if The server makes requests to internal resources when processing the HTML input, indicating no sanitization is in place
  4. Check for existing HTML sanitization
    Examine the server-side code or configuration related to the PDF conversion module. Look for any allowlist-based sanitization, Content Security Policy, or tag stripping mechanisms applied to HTML input before PDF generation.
    Affected if No sanitization is implemented or dangerous tags like iframe, img, link, script are not being stripped

You are affected if your InfoDoc version is 22547 or 22567 and the HTML-to-PDF conversion feature is enabled without proper input sanitization.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict allowlist-based HTML sanitization in the PDF conversion module, disabling or stripping dangerous tags (iframe, img with src, link, script, etc.) and preventing loading of external/local resources.

Fix this in Document On Line Submission And Approval System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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