CVE-2025-49264
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Cloud Infrastructure Services Cloud SAML SSO - Single Sign On Login cloud-sso-single-sign-on allows PHP Local File Inclusion.This issue affects Cloud SAML SSO - Single Sign On Login: from n/a through <= 1.0.18.
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 confidenceLocal File Inclusion vulnerability in Cloud SAML SSO PHP application allows attackers to include arbitrary files from the server filesystem via improper control of filename parameters in include/require statements. This can enable unauthorized reading of sensitive configuration files, credentials, and source code.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Cloud SAML SSO PHP applicationSearch your web server for files related to SAML SSO functionality. Look for PHP files containing SAML, SSO, or similar authentication logic in your web directory.Affected if The Cloud SAML SSO PHP application is present in your environment
-
Locate file inclusion pointsSearch PHP source files for include, require, include_once, or require_once statements that accept user-controlled input (e.g., parameters from GET/POST requests).Affected if File inclusion functions use parameters without proper validation
-
Check for unsanitized filename parametersExamine the code around include/require statements to see if the filename parameter is derived directly from user input (like $_GET or $_POST) without sanitization, path traversal checks, or whitelist validation.Affected if Filename parameters are passed directly from user input to include/require without validation
-
Test for directory traversal in file inclusionIf the application accepts file parameters, attempt to reference files outside the intended directory (e.g., ../../etc/passwd) to see if the application allows reading arbitrary files.Affected if The application allows directory traversal sequences to access files outside the intended directory
-
Review web server logs for suspicious file inclusion attemptsCheck access logs for patterns like '../', '..%2F', or requests to sensitive files (e.g., /etc/passwd, config files) that may indicate exploitation attempts.Affected if Log entries show requests with directory traversal patterns targeting sensitive system files
Your environment is affected if the Cloud SAML SSO PHP application uses include/require statements with filename parameters derived from user input without validation or path traversal protection.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict input validation with whitelist approach for file inclusion paths, or upgrade to a patched version if available. Apply web application firewall rules as temporary mitigation.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49264 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-49264 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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