Keywords to Links Converter SQL injection in AJAX action for authenticated users
- Exploited
- No known exploitation
- Fix
- Fixed in 2.2.5
- Who is exposed
- Not reported
Summary
The Keywords to Links Converter WordPress plugin before 2.2.5 does not sanitise and escape a parameter before using it in a SQL statement via an AJAX action available to any authenticated user, allowing users with a role as low as Subscriber to perform SQL injection attacks and read arbitrary data from the database.
What to do
Upgrade to a fixed version: 2.2.5.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-132042 (Keywords to Links Converter 2.0.0 - 2.2.4 - Subscriber+ SQL Injection), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-132042 (entry last updated 2026-11-21):
Affected:
- Unknown Keywords to Links Converter: from 2.0.0, fixed in 2.2.5
Fixed versions: 2.2.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-132042 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132042 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- the references on https://cve.now/CVE-2026-132042
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-132042
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132042"}.Affected versions
- Unknown Keywords to Links ConverterFrom 2.0.0 · fixed in 2.2.5
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 55 if added to CISA KEV
- Would score about 50 if CISA's SSVC rates exploitation active
- Would score about 22 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-132042 |
| Record | NVD · CVE-2026-132042 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | wpscan.com · vulnerability/5937ee6f-9060-46b0-9161-9129be443340 |
Questions about CVE-2026-132042
Is CVE-2026-132042 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-132042?
Keywords to Links Converter: from 2.0.0 before 2.2.5.
Source: cve.now feed data
How do I fix CVE-2026-132042?
Upgrade to a fixed version: 2.2.5.
Source: cve.now feed data
Related
- CVE-2026-132073Keywords to Links Converter < 2.2.5 - Subscriber+ Persistent Denial of Service
- CVE-2026-94259SMS Alert < 4.0.4 - Admin+ SQLi via 'ID' Parameter
- CVE-2026-14233LifterLMS < 10.0.5 - Subscriber+ Quiz Question Disclosure via query_quiz_questions
- CVE-2026-133362ThinkRank < 2.21.4 - Authenticated Cross-Section Settings Read and Update via 'category' Parameter
- CVE-2026-132814WPO365 < 45.0 - Unauthenticated Account Takeover via OIDC Audience Verification Bypass
- CVE-2026-127024WordForm < 4.1.6 - Unauthenticated Arbitrary File Upload
No corrections so far. Something wrong on this page? Report an error.