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

CVE-2025-68974

MEDIUM · 6.6 CVSS v3.1 Published 2025-12-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable 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 Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in miniOrange WordPress Social Login and Register miniorange-login-openid allows PHP Local File Inclusion.This issue affects WordPress Social Login and Register: from n/a through <= 7.7.0.

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

This is a PHP Local File Inclusion (LFI) vulnerability in the miniOrange WordPress Social Login and Register plugin (miniorange-login-openid). The vulnerability allows attackers to manipulate file path parameters in include/require statements to access sensitive local files, potentially leading to code execution. The issue affects all versions up to and including 7.7.0.

MitigationUpdate the miniOrange WordPress Social Login plugin to the latest version once available, and implement strict input validation on any parameters used in include/require statements to prevent path traversal.

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

CVSS:3.1/AV:N/AC:H/PR:H/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 if the miniOrange plugin is installed
    Access your WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'miniOrange WordPress Social Login and Register' or 'miniorange-login-openid' in the list of active plugins
    Affected if The plugin is installed and active on the WordPress site
  2. Determine the installed plugin version
    In the WordPress plugins list, click on the plugin to view its details, or inspect the plugin header in wp-content/plugins/miniorange-login-openid/miniorange_login_openid.php to find the 'Version' field
    Affected if The version listed is 7.7.0 or lower, or if no version number is displayed but the plugin is present
  3. Locate PHP files using include/require with variable paths
    Examine PHP source files in the plugin directory (wp-content/plugins/miniorange-login-openid/) for patterns like 'include($_REQUEST', 'require($_GET', or similar dynamic file inclusion statements where user input affects the file path
    Affected if Any PHP file in the plugin contains include/require statements that incorporate request parameters (GET/POST) directly into the file path without sanitization
  4. Check for accessible file inclusion endpoints
    Review the plugin's routing/endpoint handlers to identify which PHP files process incoming requests and could be reached via HTTP, then test if parameters controlling include paths can be manipulated
    Affected if The plugin exposes endpoints that accept file path parameters which can be exploited for path traversal (e.g., passing ../../../../etc/passwd)
  5. Review server access logs for suspicious requests
    Examine web server access logs (Apache/Nginx error and access logs) for patterns where the plugin's PHP files are requested with unusual path parameters, such as requests containing '../' sequences or attempts to include system files
    Affected if Logs show requests to the plugin's PHP files with path traversal sequences or attempts to access files outside the WordPress installation directory

The environment is affected if the miniOrange WordPress Social Login plugin (miniorange-login-openid) version 7.7.0 or lower is installed, and the plugin processes file path parameters in include/require statements that can be manipulated by attackers.

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

Update the miniOrange WordPress Social Login plugin to the latest version once available, and implement strict input validation on any parameters used in include/require statements to prevent path traversal.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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