CVE-2026-126697

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.4 from GitHub Security Advisory (severity: MODERATE) published 2026-11-14. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory

Also known asEUVD-2026-125869 (ENISA EUVD) · GHSA-326x-6v6x-22wv (GitHub Security Advisories)Source: ENISA EUVD

5.4EG
EchelonGraph verdictMonitorNo fix is confirmed yet: check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.4Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (WPScan) lists Quick Page/Post Redirect Plugin versions 5.2.1 up to but not including 5.2.4 as affected. No release containing a fix is confirmed on record.

The Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4 was distributed with a hidden update mechanism that fetched Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4 updates from its author's own server instead of WordPress.org, which was used to push a backdoored build to sites, allowing the attacker controlling that server to inject arbitrary content into pages and to deliver arbitrary code to affected sites.

Version 5.2.1, as published on WordPress.org, bundled the Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4 Update Checker library (updater/ directory) configured to poll https://anadnet.com/updates/?action=get_metadata&slug=quick-pagepost-redirect-Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4. In March 2021 that server delivered a modified 5.2.3 build, different from the 5.2.3 later published on WordPress.org, which kept the update channel and added a the_content filter that, for logged-out visitors on single posts and pages, fetched content from https://w.anadnet.com/bro/3/ (passing the site host, request URI and visitor User-Agent) and prepended the response to the post (observed serving SEO spam links to search engine crawlers). Because the version string matched a later WordPress.org release, affected sites were not offered a clean update until 5.2.4.

Indicators of compromise:

  • Outbound requests to anadnet.com or w.anadnet.com
  • An updater/ directory (Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4 Update Checker, Puc v4p10) inside wp-content/Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4/quick-pagepost-redirect-Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4/
  • The strings filter_the_content_in_the_main_loop, ppr_pro, QQQEND or w.anadnet.com in page_post_redirect_Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4.php
  • page_post_redirect_Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4.php with MD5 ad717da18cf8a2b69899c0d7dafee05a (tampered 5.2.3)

Remediation: remove the Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4 (it has been closed on WordPress.org), or at minimum reinstall the clean 5.2.4 from WordPress.org, delete any leftover updater/ directory, verify the files with "wp Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4 verify-checksums quick-pagepost-redirect-Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4", clear the opcode cache, and treat any site that ran the tampered build as potentially compromised.

CVSS v3
5.4
EG Score
5.4MEDIUMhigh confidence
EG Risk
39
EG Risk 39/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
9th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 14, 2026

Last Modified

November 17, 2026

Advisory Details (1)

Auto-updated Nov 16, 2026
🔬 Proof of concept available. No fix on record yet.
Web page🟡 PoC Available

Quick Page/Post Redirect 5.2.1 – 5.2.3 – Backdoor via Off-Repository Update Channel | CVE 2026-126697 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/9eb3f68c-f8ce-493f-8b0f-ddab376e0f3b/

Vendor Advisories for CVE-2026-126697(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 15× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  3. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  4. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  5. 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  6. 2026-11-17 15:48 UTCEchelonGraph re-scored
  7. 2026-11-17 15:48 UTCGHSA enrichmentGHSA-326x-6v6x-22wv · GitHub severity MODERATE · GitHub CVSS 5.4
  8. 2026-11-16 16:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-11-16 12:28 UTCGHSA enrichmentGHSA-326x-6v6x-22wv
  10. 2026-11-16 11:57 UTCEchelonGraph re-scoredFirst assessed: 5.4 MEDIUM
  11. 2026-11-16 11:57 UTCGHSA enrichmentGHSA-326x-6v6x-22wv
  12. 2026-11-16 11:54 UTCMITRE cvelistV5CVSS v3 → 5.4 · severity → MEDIUM
  13. 2026-11-15 16:57 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-11-14 16:39 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-11-14 09:46 UTCGHSA enrichmentGHSA-326x-6v6x-22wv
  16. 2026-11-14 07:01 UTCENISA EUVD ID recordedEUVD-2026-125869 · Source: ENISA EUVD
  17. 2026-11-14 06:30 UTCEchelonGraph re-scored
  18. 2026-11-14 06:20 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-126697?
CVE-2026-126697 is a medium-severity vulnerability; its CVE record was published on November 14, 2026. The Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4 was distributed with a hidden update mechanism that fetched Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4 updates from its author's own server instead of WordPress.org, which was used to push a backdoored build to…
When was the CVE record for CVE-2026-126697 published?
The CVE record for CVE-2026-126697 was published on November 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 17, 2026; the record at its source may have been updated since.
Is CVE-2026-126697 actively exploited?
CVE-2026-126697 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-126697?
CVE-2026-126697 has a CVSS v3.1 base score of 5.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-126697?
No fix for CVE-2026-126697 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (WPScan) lists Quick Page/Post Redirect Plugin versions 5.2.1 up to but not including 5.2.4 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-126697 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-126697

Explore →

Is Your Infrastructure Affected by CVE-2026-126697?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.