dbcve.org
PubliccmsApplication

CVE-2026-3289

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
A weakness has been identified in Sanluan PublicCMS 6.202506.d. This impacts the function saveMetadata of the file TemplateCacheComponent.java of the component Template Cache Generation. Executing a manipulation can lead to path traversal. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

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 · moderate confidence

Path traversal vulnerability in the saveMetadata function of TemplateCacheComponent.java in Sanluan PublicCMS 6.202506.d allows remote attackers to manipulate file paths, potentially enabling arbitrary file write or overwrite on the server through the template cache generation component.

MitigationImplement strict path validation and sanitization on the saveMetadata function to prevent directory traversal sequences; consider disabling the affected template cache functionality until vendor patch is available or deploy a WAF rule to block path traversal patterns.

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
PubliccmsApplication
Affected:= 6.202506.d

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
High
Availability
High

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

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 PublicCMS installation
    Search for PublicCMS files or check application metadata (look for 'publiccms' in deployed artifacts, WAR files, or application banner/footer)
    Affected if PublicCMS is not present, the system is not affected by this specific vulnerability
  2. Verify exact version
    Locate the version identifier in the deployment (typically in a version file, pom.xml, or application properties under the PublicCMS installation directory)
    Affected if The installed version is exactly 6.202506.d - this is the only affected version listed
  3. Check template cache component status
    Locate and inspect TemplateCacheComponent.java or the compiled class, identify if the template cache functionality is enabled in the application configuration
    Affected if Template cache generation is enabled and in use - the vulnerability exists in the saveMetadata function of this component
  4. Audit cache directory permissions and contents
    Identify the configured template cache directory (check CMS configuration files for cache path settings), list files and verify no unexpected files exist outside the intended cache directory
    Affected if Files appear outside the designated cache directory, or traversal patterns (../) are found in any stored metadata or cache file references
  5. Review access logs for path traversal patterns
    Search web server and application logs for requests containing '../' or path traversal sequences targeting template cache or metadata endpoints
    Affected if Exploitation attempts are observed in logs - the CVE has a publicly available exploit

A system is affected only if it runs PublicCMS version 6.202506.d with the template cache generation feature enabled.

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 path validation and sanitization on the saveMetadata function to prevent directory traversal sequences; consider disabling the affected template cache functionality until vendor patch is available or deploy a WAF rule to block path traversal patterns.

Fix this in Publiccms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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