Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-81779 – Critical Backdoor / Unauthenticated Remote Code Execution – Newspapers X WordPress

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-81779 is a critical supply-chain backdoor vulnerability affecting the Newspapers X WordPress theme by Silk Themes. Versions 1.0.46 through 1.0.48 of the theme shipped with malicious code distributed through the vendor’s official update channel, allowing unauthenticated remote attackers to gain persistent, unauthorized access to affected WordPress sites. The vulnerability carries a maximum CVSS v3.1 base score of 10.0 (Critical).

Technical details

  • Root cause: the theme package itself was compromised, with a malicious more-functions.php file and associated backdoor mechanisms bundled into three consecutive official releases (1.0.46, 1.0.47, 1.0.48).
  • Trigger condition: simply installing or running one of the affected theme versions activates the embedded backdoor — no additional configuration or user action is required.
  • Attack vector: Network (AV:N), no privileges required (PR:N), no user interaction required (UI:N), low attack complexity (AC:L).
  • Impact: full compromise of confidentiality, integrity, and availability (C:H/I:H/A:H) with a changed scope (S:C). Attackers can execute arbitrary payloads, inject content (e.g., unauthorized advertisements), create or leverage backdoor access, and maintain persistence on the compromised site.
  • Classified under CWE-1284 (Improper Validation of Specified Quantity in Input) and CAPEC-523 (Malicious Software Implanted).

Affected software

  • Newspapers X WordPress theme (Silk Themes), package newspapers-x, versions 1.0.46 through 1.0.48.

Severity

  • CVSS v3.1 Base Score: 10.0 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Update the Newspapers X theme to version 1.0.49 or later, where the malicious code has been removed.
  • If already running an affected version: treat the site as compromised — remove any backdoor files (including more-functions.php if present), audit and remove rogue/unrecognized administrator accounts, rotate all credentials and secret keys, and review site content and file integrity for unauthorized changes.
  • Where immediate patching is not possible, take the affected site offline or restrict external access until remediation is complete, and restore from a known-clean backup if available.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: /wp-content/themes/newspapers-x/

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge