dbcve.org
Pad CmsApplication · Widzialni

CVE-2025-8116

MEDIUM · 6.1 CVSS v3.1 Published 2025-09-30
Fix available
A fix is available. Upgrade to after 1.2.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
PAD CMS is vulnerable to Reflected XSS in printing and save to PDF functionality. Malicious attacker can craft special URL, which will result in arbitrary JavaScript execution in victim's browser, when opened. This issue affects all 3 templates: www, bip and www+bip. This product is End-Of-Life and producent will not publish patches for this vulnerability.

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

PAD CMS contains a reflected cross-site scripting (XSS) vulnerability in its printing and 'save to PDF' functionality across all three templates (www, bip, www+bip). Attackers can craft malicious URLs containing JavaScript payloads that get reflected back and executed in victim browsers when the URL is opened.

MitigationSince the vendor will not issue patches (EOL product), implement a WAF with XSS filtering rules to sanitize URL parameters, disable the vulnerable printing/PDF features if feasible, or migrate to a supported CMS platform.

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
Pad CmsApplication
Affected:<= 1.2.1

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Confirm PAD CMS installation
    Check for PAD CMS files in the web root directory, typically looking for directories like 'pad-cms', 'cms', or files with 'widzialni' in the name. Also check the HTML source for 'widzialni' or 'PAD CMS' branding in the footer.
    Affected if The product files are present on the server.
  2. Identify installed version
    Check for version information in the CMS admin panel (usually in Settings > About or System Info), or examine version files in the installation directory such as version.php, config.php, or a CHANGELOG file.
    Affected if The installed version is 1.2.1 or lower.
  3. Verify printing feature is accessible
    Attempt to access the print functionality by navigating to pages on the site and looking for a print button, print-friendly view, or URL parameters containing 'print', 'pdf', or 'save' in the request. Test by adding '?print=1' or '?pdf=1' to page URLs.
    Affected if The printing or PDF generation feature is enabled and responds to requests.
  4. Test for reflected XSS in print/PDF URLs
    Craft a test URL with a benign XSS payload in the URL parameters used by the print/PDF feature, such as '?print=<script>alert(1)</script>' or '?pdf=<img src=x onerror=alert(1)>'. Inspect the page source to see if the payload is reflected unescaped.
    Affected if The payload is reflected directly into the HTML output without encoding or sanitization.
  5. Check template configuration
    Examine the CMS configuration for active templates (www, bip, or www+bip) in the template settings or config files. The vulnerability affects all three templates.
    Affected if Any of the three templates (www, bip, or www+bip) are active.

A system is affected if it runs Widzialni Pad CMS version 1.2.1 or lower with the printing or PDF feature enabled and templates (www, bip, or www+bip) active, where URL parameters are reflected unescaped in print/PDF functionality.

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 a release after 1.2.1
Interim mitigation

Since the vendor will not issue patches (EOL product), implement a WAF with XSS filtering rules to sanitize URL parameters, disable the vulnerable printing/PDF features if feasible, or migrate to a supported CMS platform.

Recommended fix High confidence
  1. This is an End-Of-Life product with no vendor patches available.
  2. Consider migrating to an actively maintained CMS solution.
  3. If continued use is required, implement a Web Application Firewall (WAF) to help filter malicious requests.
  4. Implement Content Security Policy (CSP) headers to help mitigate XSS impact.
  5. Educate users about not clicking on untrusted links that could contain malicious payloads.

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

Fix this in Pad Cms Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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