LiveActive security incident?Get immediate response
CVE Record

CVE-2026-2503: ElementCamp <= 2.3.6 - Authenticated (Author+) SQL Injection via 'meta_query[compare]' Parameter

The ElementCamp plugin for WordPress is vulnerable to time-based SQL Injection via the 'meta_query[compare]' parameter in the 'tcg_select2_search_post' AJAX action in all versions up to, and including, 2.3.6. This is due to the user-supplied compare value being placed as an SQL operator in the query without validation against an allowlist of comparison operators. The value is passed through esc_sql(), but since the payload operates as an operator (not inside quotes), esc_sql() has no effect on payloads that don't contain quote characters. This makes it possible for authenticated attackers, with Author-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

ElementCamp for WordPress has an authenticated SQL injection issue in versions up to 2.3.6. An attacker needs an Author-level or higher account, but could potentially read sensitive database information. This matters most for sites with many content contributors, weak account controls, or any chance of compromised author accounts.

Executive priority

Treat as a near-term remediation item, especially on externally accessible WordPress sites with multiple authors. It is not currently supported as actively exploited, but it can expose database information if an author account is abused or compromised.

Technical view

CVE-2026-2503 is a time-based SQL injection in the ElementCamp AJAX action tcg_select2_search_post. The meta_query[compare] value is used as an SQL operator without allowlist validation. Although esc_sql() is applied, the source states it does not protect operator-position input that lacks quotes. CVSS is 6.5, CWE-89.

Likely exposure

WordPress sites running ElementCamp up to and including 2.3.6 are the stated exposure. Exploitation requires authenticated WordPress access with Author privileges or higher. Public-facing sites with contributor workflows or compromised author accounts have higher practical risk.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The issue is network-reachable after login, low complexity, and no user interaction is required. Impact is primarily confidentiality: extracting sensitive database information.

Researcher notes

The source description is detailed on root cause and affected range, but the bundle does not provide a specific fixed version. The affected metadata appears inconsistent, so rely on the narrative, Wordfence entry, and WordPress Trac references while confirming current vendor status.

Mitigation direction

  • Inventory WordPress sites for the ElementCamp plugin and installed version.
  • Check vendor or WordPress plugin guidance for a release newer than 2.3.6.
  • Update ElementCamp when a fixed version is available from trusted channels.
  • Temporarily disable ElementCamp where update is unavailable and exposure is unacceptable.
  • Limit Author-level and higher accounts to trusted users only.
  • Review and revoke unused, shared, or suspicious WordPress contributor accounts.

Validation and detection

  • Confirm whether ElementCamp is installed on each WordPress site.
  • Record the installed ElementCamp version and flag versions up to 2.3.6.
  • Review WordPress roles for users with Author privileges or higher.
  • Check web logs for unusual authenticated admin-ajax.php activity involving tcg_select2_search_post.
  • Monitor for abnormal database response timing or suspicious authenticated plugin requests.
  • Recheck vendor advisories for confirmed fixed-version information.
Prepared
Confidence
medium
Sources
7

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-2026-2503 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
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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
4Source 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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2026-2503Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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
Affected products

Products and packages named in the record

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