Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2014-125133: Unauthenticated Path Traversal in NativeChurch WordPress Theme

Published Oct 20, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 2 in a dayToday
CVSS8.7High · v4
EPSS1.1%67th percentile
CISA KEVNoNot listed
In the wildReported4 exploitation records in Mallory
IdentifiersCVE-2014-125133CWE-22 · Improper Limitation of a Pathname…

The NativeChurch theme for WordPress before version 1.6.2 contains a path traversal vulnerability in its file download handler. Unauthenticated attackers can submit GET requests containing directory traversal sequences in the file parameter to retrieve arbitrary files accessible to the web server process, including sensitive WordPress configuration data. Exploitation was first observed by the Shadowserver Foundation on October 19, 2023.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises the confidentiality of files readable by the web server process. Disclosure of WordPress configuration data can expose database credentials and other configuration secrets, potentially enabling further compromise depending on credential validity, reuse, and service accessibility.

Mitigation

If you can’t patch tonight, do this now.

Until the update can be applied, block access to the affected theme's download.php endpoint. No other workaround is specified.

Remediation

Patch, then assume compromise.

Upgrade the NativeChurch WordPress theme to version 1.6.2 or later.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2014-125133 exploited in the wild?
Yes. As of Nov 22, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2014-125133?
Yes. As of Nov 22, 2026, Mallory has reports of a public exploit for CVE-2014-125133.
Is there a patch for CVE-2014-125133?
Upgrade the NativeChurch WordPress theme to version 1.6.2 or later.
How severe is CVE-2014-125133?
CVE-2014-125133 has a CVSS v4 score of 8.7 (High) and an EPSS score of 1.1% (67th percentile) as of Nov 22, 2026.
Activity feed

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.