dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-69107

HIGH · 8.1 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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
Unauthenticated Local File Inclusion in Rosaleen <= 2.8 versions.

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

Unauthenticated Local File Inclusion (LFI) vulnerability in Rosaleen <= 2.8 allows remote attackers to read sensitive files on the server filesystem without any authentication. The vulnerability stems from improper input validation on file inclusion parameters, enabling path traversal attacks.

MitigationUpgrade Rosaleen to a version beyond 2.8. If immediate upgrade is not possible, implement strict whitelist-based input validation on all file inclusion parameters and disable allow_url_fopen/allow_url_include in PHP configurations.

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

CVSS:3.1/AV:N/AC:H/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 Rosaleen installation and version
    Locate the Rosaleen application on the server and check its version number. Common locations include: a version file (version.php, VERSION), the main index file header comment, composer.json, or the admin dashboard About page. Compare the found version against the affected range (anything <= 2.8).
    Affected if Rosaleen version 2.8 or lower is installed
  2. Confirm the application is web-accessible
    Verify the Rosaleen web application is exposed and reachable via HTTP/HTTPS. Attempt to access the main entry point (index.php or similar) to confirm the application responds.
    Affected if The Rosaleen application is accessible over the network without authentication required for basic access
  3. Locate file inclusion functionality
    Inspect the Rosaleen source code for functions that include or require files based on user input. Search for patterns like include(), require(), include_once(), require_once() that use variables or request parameters. Identify which parameters control the file path.
    Affected if The application contains file inclusion logic that accepts user-supplied input for file paths
  4. Test unauthenticated access to file inclusion parameters
    If file inclusion parameters are identified (e.g., ?page=, ?file=, ?template=), attempt to craft path traversal requests (e.g., ../../../../etc/passwd) without providing any authentication credentials. Verify whether the application processes these requests.
    Affected if File inclusion parameters can be manipulated via path traversal without authentication

The environment is affected if Rosaleen version 2.8 or lower is running and file inclusion parameters accepting user input are accessible 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 Rosaleen to a version beyond 2.8. If immediate upgrade is not possible, implement strict whitelist-based input validation on all file inclusion parameters and disable allow_url_fopen/allow_url_include in PHP configurations.

Recommended fix Moderate confidence

Rosaleen 2.9 or later (verify latest stable release)

  1. 1. Identify the current Rosaleen version in use by checking the application's version file or admin interface
  2. 2. Obtain the latest fixed version of Rosaleen from the official vendor or repository
  3. 3. Review release notes or security advisories for version 2.9 or higher to confirm the LFI vulnerability is addressed
  4. 4. Back up the entire application database and files before upgrading
  5. 5. Deploy the upgraded Rosaleen version (2.9 or later) to the production environment
  6. 6. Verify the file inclusion functions are properly secured after upgrade
  7. 7. Test that the application functions correctly post-upgrade
Caveat Review changelog for potential breaking changes between 2.8 and the target upgrade version

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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