LiveActive security incident?Get immediate response
CVE Record

CVE-2022-2460: WPDating < 7.4.0 - Multiple Unauthenticated SQLi

The WPDating WordPress plugin before 7.4.0 does not properly escape user input before concatenating it to certain SQL queries, leading to multiple SQL injection vulnerabilities exploitable by unauthenticated users

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-2460 affects the WPDating WordPress plugin before 7.4.0. A public website using a vulnerable version could allow unauthenticated attackers to influence database queries. The provided CVSS score is medium, with integrity impact identified and no confidentiality or availability impact in the vector.

Executive priority

Treat this as a focused WordPress plugin remediation item, not a broad enterprise crisis. Internet-facing dating or membership sites using WPDating before 7.4.0 should be updated promptly because unauthenticated SQL injection has public technical coverage.

Technical view

The issue is CWE-89 SQL injection caused by insufficient escaping of user input before concatenation into SQL queries. The source bundle states multiple unauthenticated SQL injection vulnerabilities in WPDating before 7.4.0. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N, score 4.3.

Likely exposure

Exposure is limited to WordPress sites running the WPDating plugin before version 7.4.0. The bundle lists no CPEs and vendor details are incomplete, so asset confirmation must come from WordPress/plugin inventory.

Exploitation context

The WPScan reference is tagged as an exploit and technical description source, but the bundle does not state observed active exploitation. CISA KEV is false, so active exploitation is not established from the provided evidence.

Researcher notes

The provided data supports WPDating before 7.4.0 as affected and maps the flaw to CWE-89. Affected vendor metadata is weak, CPEs are absent, and active exploitation is not evidenced. Avoid assuming database disclosure because the supplied CVSS vector lists no confidentiality impact.

Mitigation direction

  • Upgrade WPDating to version 7.4.0 or later where deployed.
  • Confirm current vendor guidance for any additional remediation notes.
  • Disable or remove WPDating if an upgrade cannot be completed promptly.
  • Prioritize internet-facing WordPress sites and high-business-value properties first.

Validation and detection

  • Inventory all WordPress sites for installed WPDating versions.
  • Confirm no deployed WPDating instance is below 7.4.0.
  • Review plugin and WordPress logs for unusual unauthenticated request patterns.
  • Document remediation status for each affected site.
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-2460 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
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

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

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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2022-2460Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
UnknownWPDating0unaffected
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.