CVE-2025-49255
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 thembay Ruza ruza allows PHP Local File Inclusion.This issue affects Ruza: from n/a through <= 1.0.7.
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 thembay Ruza allows attackers to include arbitrary local files via improper control of filename parameters in PHP include/require statements, potentially exposing sensitive server files or enabling code execution.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify thembay Ruza installationSearch for files named 'ruza', 'themabay', or look for theme/template directories containing 'Ruza' in the web root. Check composer.json, theme.json, or style.css headers for product identification.Affected if The thembay Ruza theme or template is present on the server
-
Determine installed versionCheck version files in the theme root (version.php, theme.json, style.css header, or composer.json). Compare against any published version numbers for the product.Affected if Version cannot be determined or falls within an unpatched release range
-
Locate PHP file inclusion patternsSearch the Ruza codebase for include, include_once, require, or require_once statements. Use grep or similar: grep -r 'include\|require' --include='*.php' in the theme directory.Affected if PHP files containing include/require statements are found in the Ruza installation
-
Check for user input in file inclusionExamine the identified include/require statements for direct or indirect use of $_GET, $_POST, $_REQUEST, or other user-supplied parameters in the file path.Affected if User-controllable parameters are used in include/require statements without evident sanitization or validation
-
Verify exposed file inclusion endpointsIdentify PHP scripts that handle file inclusion and check if they are accessible via web requests. Test with benign paths like ../../../../etc/passwd (if safe to do so) to confirm vulnerability.Affected if File inclusion scripts are web-accessible and accept unsanitized filename parameters
The environment is affected if thembay Ruza is installed and contains PHP code where user-supplied input reaches include/require statements without validation, allowing arbitrary file inclusion.
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 using allowlists for file inclusion paths, sanitize all user-supplied filename parameters, and avoid direct use of user input in include/require statements. Upgrade to patched version when available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-49255 — 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-49255 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