dbcve.org
CWE-538Weakness · CWE-538

CVE-2025-12059

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-11
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
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
Insertion of Sensitive Information into Externally-Accessible File or Directory vulnerability in Logo Software Industry and Trade Inc. Logo j-Platform allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Logo j-Platform: from 3.29.6.4 before 3.34.8.9.

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

Logo j-Platform versions 3.29.6.4 through 3.34.8.8 contain an access control misconfiguration that allows sensitive information to be written to or exposed through externally-accessible files or directories. This critical vulnerability (CVSS 9.8) likely allows unauthenticated attackers to access configuration files, credentials, or other sensitive data stored in web-accessible locations due to incorrectly configured security levels.

MitigationUpgrade Logo j-Platform to version 3.34.8.9 or later. Additionally, review and restrict web-accessible directories to ensure only intended files are externally reachable, and audit for any exposed sensitive data.

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

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. Identify installed Logo j-Platform version
    Locate the version information for your Logo j-Platform installation (typically found in application metadata, about page, or installation directory)
    Affected if the installed version falls within 3.29.6.4 through 3.34.8.8
  2. Review web-accessible directories
    Inspect your web server configuration and document root to identify directories that are served externally
    Affected if sensitive directories or files are located within publicly accessible web paths
  3. Audit file placement for sensitive data
    Scan publicly accessible directories for configuration files, credentials, business documents, or other sensitive data that should not be web-exposed
    Affected if sensitive files are found in externally accessible locations
  4. Test access control on sensitive paths
    Attempt to retrieve potential sensitive files via HTTP/HTTPS requests without authentication
    Affected if files containing sensitive information are accessible without authentication

You are affected if your Logo j-Platform version is between 3.29.6.4 and 3.34.8.8 AND sensitive files are accessible via web requests without authentication.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Logo j-Platform to version 3.34.8.9 or later. Additionally, review and restrict web-accessible directories to ensure only intended files are externally reachable, and audit for any exposed sensitive data.

Recommended fix High confidence

Logo j-Platform 3.34.8.9 or later

  1. 1. Backup all Logo j-Platform data and configurations before initiating the upgrade.
  2. 2. Download Logo j-Platform version 3.34.8.9 or later from the official Logo Software vendor.
  3. 3. Install the upgrade in a non-production environment to verify compatibility and functionality.
  4. 4. After successful testing in the staging environment, schedule a maintenance window for production deployment.
  5. 5. Deploy the upgrade to production systems.
  6. 6. Verify the installation by confirming the running version is 3.34.8.9 or later.
  7. 7. Test critical business workflows to ensure the upgrade did not introduce regressions.
  8. 8. Review system logs to confirm the vulnerability has been remediated and no sensitive information is being exposed in externally accessible files.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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