CVE-2026-22512
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 Elated-Themes Roisin roisin allows PHP Local File Inclusion.This issue affects Roisin: from n/a through <= 1.2.1.
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 Elated-Themes Roisin allows attackers to include arbitrary local PHP files through unsanitized input parameters in include/require statements. This can lead to remote code execution if attackers can control the included files or upload malicious PHP files to accessible locations.
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.
-
Confirm Roisin theme installation and versionAccess WordPress dashboard > Appearance > Themes, or inspect the style.css file in wp-content/themes/roisin/ to find the Theme Name and Version headersAffected if Roisin theme is active and the installed version lacks the security patch (compare your version to any patched version the vendor releases)
-
Identify vulnerable include/require patternsSearch theme PHP files for include, include_once, require, or require_once statements that use $_GET, $_POST, or $_REQUEST variables directly without sanitization (e.g., 'include($_GET["page"])' or 'require($param)')Affected if Any PHP file contains include/require statements that incorporate unsanitized user-supplied input parameters
-
Review file upload functionalityCheck for any custom upload forms, AJAX handlers, or third-party plugins within the theme that accept file uploads; inspect upload directories (typically wp-content/uploads/) for suspicious PHP filesAffected if File upload capability exists in the theme or its bundled plugins, allowing PHP files to be placed in web-accessible locations
-
Verify PHP configuration settingsCreate a PHP info file (<?php phpinfo(); ?>) or check php.ini for the allow_url_include setting; also verify if open_basedir restrictions are in placeAffected if allow_url_include is enabled (increases exploitability) or no open_basedir restrictions exist to limit file access
-
Audit WordPress debug and error logsReview wp-content/debug.log (if debugging is enabled) and server error logs for repeated include/require failures that may indicate active exploitation attemptsAffected if Logs show requests with unusual file paths in query parameters targeting include/require functions
A user is affected if the Roisin theme is installed and the codebase contains include/require statements using unsanitized $_GET, $_POST, or $_REQUEST parameters, combined with the ability for attackers to either manipulate file paths or upload malicious PHP files to accessible directories.
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 dataUpgrade to a patched version of Roisin theme. If no patch is available, implement strict input validation with whitelist approach for file inclusion paths, disable allow_url_include, and review code for vulnerable include/require patterns using user-supplied input.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2026-22512 — 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-2026-22512 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