dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-15066

MEDIUM · 6.2 CVSS v3.1 Published 2025-12-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), Missing Authorization vulnerability in Innorix WP allows Path Traversal.This issue affects Innorix WP from All versions If the "exam" directory exists under the directory where the product is installed (ex: innorix/exam)

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

A path traversal vulnerability exists in Innorix WP where the application fails to properly validate path inputs when an 'exam' directory exists under the installation directory (e.g., innorix/exam), combined with missing authorization checks. This allows attackers to access files outside the intended restricted directory through path manipulation.

MitigationRemove or restrict access to the 'exam' directory if not required for functionality, and implement proper path validation (canonicalization checks) along with authorization verification before file operations to prevent directory traversal attacks.

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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/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 if Innorix WP is installed
    Search for innorix installation directories on the system. Common locations include web root directories (e.g., /var/www/, /inetpub/, C:\inetpub\), or check for files containing 'innorix' in the filename or application directories.
    Affected if Innorix WP software is found on the system
  2. Locate the exam directory
    Within the identified innorix installation directory, check for the presence of an 'exam' subdirectory (e.g., innorix/exam, /innorix/exam, or similar path depending on installation structure).
    Affected if An 'exam' directory exists within the innorix installation folder
  3. Verify web service is accessible
    Attempt to access the Innorix WP application via HTTP/HTTPS to confirm it is running and accepting requests. Check if the application responds on its expected port (commonly 80, 443, or a configured web server port).
    Affected if The Innorix WP web application is running and reachable over the network
  4. Check for path traversal exposure
    If the exam directory exists and the application is running, send a crafted request with path traversal sequences (e.g., ../../) targeting the exam functionality to see if unauthorized file access is possible. Review application logs for any path traversal attempts or unusual file access patterns.
    Affected if The application permits directory traversal via the exam endpoint allowing access to files outside the intended restricted directory
  5. Review authorization configuration
    Examine the application's configuration files or settings related to authorization and access control, specifically for the exam module or file operation functions. Check if authentication and authorization are enforced before file operations.
    Affected if Authorization checks are missing or improperly configured for file operations in the exam functionality

A user is affected if Innorix WP is installed with the exam directory present and the application allows path traversal via the exam module without proper authorization checks.

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

Remove or restrict access to the 'exam' directory if not required for functionality, and implement proper path validation (canonicalization checks) along with authorization verification before file operations to prevent directory traversal attacks.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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