CVE-2026-27326
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 axiomthemes AC Services | HVAC, Air Conditioning & Heating Company WordPress Theme window-ac-services allows PHP Local File Inclusion.This issue affects AC Services | HVAC, Air Conditioning & Heating Company WordPress Theme: from n/a through <= 1.2.5.
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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the AC Services HVAC WordPress theme by axiomthemes. The vulnerability allows attackers to manipulate filename parameters in PHP include/require statements to read sensitive local files or potentially execute arbitrary PHP code if file upload capabilities exist on the server.
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 AC Services theme is installedNavigate to WordPress dashboard > Appearance > Themes, or check /wp-content/themes/ directory for 'ac-services' folderAffected if The AC Services theme by axiomthemes is present in the WordPress installation
-
Identify installed theme versionCheck theme style.css header for 'Version:' value, or look for version in theme's functions.phpAffected if Version cannot be determined or is earlier than patched version (compare to latest available)
-
Locate vulnerable include/require usageSearch theme files for dynamic include/require statements using variables or request parameters (e.g., include($_GET['...'], require($_REQUEST['...'])Affected if Theme code contains include/require statements that incorporate user-controlled input without sanitization
-
Identify exposed vulnerable parametersReview PHP files for parameters that could be manipulated (common names: file, page, template, include, path, lang) passed via GET/POSTAffected if URL parameters exist that could be manipulated to perform directory traversal (e.g., ../../) to reach arbitrary files
-
Test for LFI accessibilityIf vulnerable parameters identified, attempt safe verification: check if the parameter accepts path traversal and includes PHP files from theme directoriesAffected if The parameter accepts directory traversal sequences and can be used to include files outside intended directory
Environment is affected if AC Services theme is installed and contains dynamic include/require statements using unsanitized user input that can be manipulated for directory traversal.
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 dataUpdate the AC Services theme to a patched version if available, or remove and replace the theme with a secure alternative. Review the web server for signs of compromise.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27326 — 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-27326 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