Security readout for executives and security teams
Plain-English summary
Link Factory is described as a WordPress backdoor disguised as a homepage sentence publisher. An installed copy could give the operator extensive control over the website, threatening confidentiality, content integrity, availability, and potentially connected business systems.
Executive priority
Treat every confirmed installation as a potential compromise, not merely vulnerable software. Prioritize immediate isolation, evidence preservation, credential rotation, and incident-response review. Business-critical or internet-facing WordPress sites should receive the highest urgency.
Technical view
The plugin exposes an operator-controlled REST API at /wp-json/link-factory/v1/. Requests are authenticated using detached Ed25519 signatures checked against a hardcoded operator public key; the health check is exempt. The supplied CVSS 3.1 score is 10.0, with network access, low complexity, no privileges, no user interaction, and impacts across security boundaries.
Likely exposure
Exposure is limited to WordPress environments where Link Factory is installed. The bundle identifies version 0 but gives an unknown default status and no CPEs, so the complete affected-version range cannot be established. Internet-facing installations are especially concerning because the API is network-accessible.
Exploitation context
The plugin is characterized as an intentional backdoor, and WPScan is tagged as containing exploit-related information. However, the bundle reports that CVE-2026-15413 is not in KEV and provides no cited evidence of active exploitation. Real-world exploitation status therefore remains unconfirmed.
Researcher notes
CWE-912 indicates hidden or undocumented functionality. The hardcoded Ed25519 public key creates an operator-only trust mechanism rather than normal site administration. The health-check exception may permit unauthenticated discovery. The source bundle does not establish the API’s complete capabilities, distribution scope, installation count, affected-version range, or observed use against victims.
Mitigation direction
- Immediately isolate WordPress sites where Link Factory is installed.
- Preserve relevant evidence before removing the plugin.
- Remove Link Factory and follow any available authoritative incident-response guidance.
- Rotate administrative credentials, API keys, and secrets accessible from affected sites.
- Rebuild from a trusted baseline if investigation indicates unauthorized control or persistent compromise.
Validation and detection
- Inventory WordPress installations for the Link Factory plugin and related files.
- Check whether /wp-json/link-factory/v1/ is exposed on each site.
- Review web and application logs for unexpected requests to that API namespace.
- Inspect affected sites for unauthorized users, content changes, persistence, or outbound connections.
- Confirm removal and verify the API namespace is no longer reachable.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-912: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-15413 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96WPScanVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/4cad269d-0146-4ca9-a1ae-55f02c8e5433/CVE reference, WPScan · exploit, vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Hidden Functionality
Hidden Functionality represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.