LiveActive security incident?Get immediate response
CVE Record

CVE-2022-47605: WordPress Custom 404 Pro Plugin <= 3.7.0 is vulnerable to SQL Injection (SQLi)

Auth. SQL Injection') vulnerability in Kunal Nagar Custom 404 Pro plugin <= 3.7.0 versions.

HighCVSS 8.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Custom 404 Pro for WordPress versions up to 3.7.0 is reported vulnerable to authenticated SQL injection. The business risk is unauthorized database access or changes by someone with high privileges and required interaction, so exposure is narrower than unauthenticated plugin flaws but impact can be serious.

Executive priority

Treat this as a high-priority WordPress plugin exposure where the plugin is installed, especially on revenue, customer, or public-facing sites. It is not currently supported as actively exploited by the provided sources.

Technical view

CVE-2022-47605 is a CWE-89 SQL injection in Kunal Nagar Custom 404 Pro <=3.7.0. CVSS 3.1 is 8.3 high: network reachable, low complexity, high privileges required, user interaction required, unchanged scope, high confidentiality and integrity impact, low availability impact.

Likely exposure

Exposure is limited to WordPress sites using the Custom 404 Pro plugin at version 3.7.0 or earlier. The source bundle does not identify a fixed version, affected endpoint, or default vulnerable configuration beyond the plugin/version statement.

Exploitation context

The CVE is not listed as CISA KEV in the supplied data, and no provided source claims active exploitation. The CVSS vector indicates exploitation requires high privileges and user interaction, reducing broad opportunistic risk but leaving concern for compromised administrator accounts.

Researcher notes

Evidence is concise: CVE metadata and Patchstack identify authenticated admin SQL injection, but do not provide affected parameters, proof-of-concept details, or a fixed version in the supplied bundle. Avoid assuming exploitability beyond PR:H and UI:R.

Mitigation direction

  • Inventory WordPress sites for the Custom 404 Pro plugin and version.
  • Check vendor or Patchstack guidance for a fixed release or official remediation.
  • Disable or remove the plugin if no confirmed fixed version is available.
  • Restrict administrator access and enforce MFA for WordPress privileged accounts.
  • Monitor database and WordPress admin activity for suspicious changes.

Validation and detection

  • Confirm whether package custom-404-pro is installed on each WordPress site.
  • Record installed versions and flag 3.7.0 or earlier for remediation.
  • Review administrator account activity during the suspected exposure window.
  • Check security tooling for SQL injection alerts tied to WordPress admin activity.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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 lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-47605 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:L

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:L0.95.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.3High
CVSS 3.1 vector shape for CVE-2022-47605Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Kunal NagarCustom 404 Procustom-404-pro, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.