Aora local file inclusion in WordPress theme
Affects the WordPress Aora theme version 1.3.5 and earlier. CVSS rates it High (8.1); no vendor rating is given. Fixed in 1.3.24.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.3.24
- Who is exposed
- Not reported
Summary
The Aora theme for WordPress from thembay has a local file inclusion flaw that lets an attacker make the software load files from the server's own file system. It can be reached remotely over the network without logging in.
Written by a model
Original description
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in thembay Aora aora allows PHP Local File Inclusion.This issue affects Aora: from n/a through 1.3.5.
Who should check
Teams running the WordPress Aora theme (thembay Aora) at version 1.3.5 or earlier, such as WordPress sites and hosts
“WordPress Aora Theme <= 1.3.5 is vulnerable to a high priority Local File Inclusion”
What to do
Upgrade to a fixed version: 1.3.24.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-131795 (WordPress Aora theme <= 1.3.5 - Local File Inclusion vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-131795 (entry last updated 2026-11-20):
Affected:
- thembay Aora: fixed in 1.3.24
Fixed versions: 1.3.24.
Conditions (all must be true for the bug to be hit):
- WordPress Aora theme version 1.3.5 or earlier (source: https://patchstack.com/database/wordpress/theme/aora/vulnerability/wordpress-aora-theme-1-3-5-local-file-inclusion-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-131795 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131795 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/theme/aora/vulnerability/wordpress-aora-theme-1-3-5-local-file-inclusion-vulnerability?_s_id=cve
- https://www.cve.org/CVERecord?id=CVE-2026-131795
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-131795
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131795"}.Affected versions
- aorafixed in 1.3.24 · through 1.3.5
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.1/10CVSS 8.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131795 |
| Record | NVD · CVE-2026-131795 |
| Other links 1 | |
| Link | patchstack.com · database/wordpress/theme/aora/vulnerability/wordpress-aora-theme-1-3-5-local-file-inclusion-vulnerability?_s_id=cve |
Questions about CVE-2026-131795
Is CVE-2026-131795 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The Aora theme lets an attacker make the site load server files it should not. This can sometimes lead to a full site takeover.
Source: patchstack.com, cve.org
Which versions are affected by CVE-2026-131795?
aora: through 1.3.5 (fixed in 1.3.24).
Source: cve.now feed data
Am I affected, and how do I check?
Aora theme versions 1.3.5 and earlier are affected. You can check the installed version in the theme's style.css header or under Appearance, Themes in the WordPress admin.
Source: patchstack.com, cve.org
How do I fix CVE-2026-131795?
Update the Aora theme to version 1.3.24 or later, the latest available version, as the fix.
Source: patchstack.com, cve.org
Related
- CVE-2026-27381WordPress Aora theme <= 1.3.15 - Local File Inclusion vulnerability
- CVE-2025-49260WordPress Aora theme <= 1.3.9 - Local File Inclusion Vulnerability
- CVE-2025-68985WordPress Aora theme <= 1.3.15 - Local File Inclusion vulnerability
- CVE-2026-66612WordPress Aora theme <= 1.3.19 - Cross Site Scripting (XSS) vulnerability
- CVE-2025-68545WordPress Nika theme <= 1.2.14 - Local File Inclusion vulnerability
- CVE-2025-68543WordPress Diza theme <= 1.3.15 - Local File Inclusion vulnerability
No corrections so far. Something wrong on this page? Report an error.