Magic Link < 2.2.6 - Subscriber+ Privilege Escalation via Magic Link Generation
- Exploited
- No known exploitation
- Fix
- Fixed in 2.2.6
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.2.6.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.14% · 3rd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 13/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The Magic Link WordPress plugin lets any logged-in user, including a low-privileged subscriber, generate a working login link for an administrator and use it to log in as that administrator. The attack needs a logged-in account on the site, and the flaw is in the plugin's failure to check whether the requester is allowed to create a link for the chosen account.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
The Magic Link WordPress plugin before 2.2.6 does not check that the user requesting a login link is authorised to generate one for the chosen account, allowing any authenticated user, such as a subscriber, to generate a working login link for an administrator and log in as them.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.8/10CVSS 8.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.2.6.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Unknown Magic Link
fixed in 2.2.6
Evidence 1
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121848
Is CVE-2026-121848 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
Which versions are affected by CVE-2026-121848?
Magic Link: before 2.2.6.Source: cve.now feed data
How do I fix CVE-2026-121848?
Upgrade to a fixed version: 2.2.6.Source: cve.now feed data