Vulnerability report

Exploitation Attempts Observed in the Wild High Confidence Not in CISA KEV

CVE-2026-95610

WordPress UpSolution Core plugin <= 9.3 - SQL Injection vulnerability

UpSolution Core · 0 to <= 9.3

Watch CVE-2026-95610 Browse KEV feed
Severity
CVSS 8.5 · High
Confidence
High
Exploit status
Exploitation Attempts Observed in the Wild
EPSS
0.2%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2026-95610 is WordPress UpSolution Core plugin <= 9.3 - SQL Injection vulnerability. Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in UpSolution UpSolution Core...

Have exploitation attempts been observed?

Yes. Exploitation attempts have been reported for this vulnerability. Previdian lists it as a known exploited vulnerability. Also reported by third-party sources. Confidence is high.

Who is affected?

UpSolution Core 0 to <= 9.3.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

WordPress UpSolution Core plugin <= 9.3 - SQL Injection vulnerability

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in UpSolution UpSolution Core us-core allows Blind SQL Injection.This issue affects UpSolution Core: from n/a through 9.3.

UpSolution Affected
UpSolution Core us-core
Through 9.3
Published
09 Oct 2026
Exploitation Attempts Reported
27 Oct 2026
Attack vector
Remote
Complexity
Low
Privileges
Low
User interaction
None

Tags

wordpress

CVE References

  • CVE Record CVE.org · CVE Record https://www.cve.org/CVERecord?id=CVE-2026-95610
  • VDB Entry — patchstack.com patchstack.com · VDB Entry https://patchstack.com/database/wordpress/plugin/us-core/vulnerabilit...

Exploitation evidence

Evidence of exploitation attempts

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploitation Attempts Observed in the Wild

CVE

Recorded 27 Oct 2026

A trusted third party reported exploitation attempts.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
CVE First 2026-10-27 13:31 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

No detection artifacts or sensor request patterns are available for this CVE yet.

Check back as sensor telemetry and scanner integrations are updated.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

8.5 High

Potential damage if exploited. Separate from whether attackers are using it.

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

EPSS

0.2%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Weaknesses

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

Timeline

From disclosure to observed exploitation attempts

  1. 13:31 UTC

    Added to Previdian KEV Feed

    High-confidence, third-party report of exploitation attempts

  2. 10:00 UTC

    CVE published

    Vulnerability disclosed publicly

  3. 09:18 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

Start 14-day Pro trial Read API docs
  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2026-95610

Sample API response 
{
  "cve_id": "CVE-2026-95610",
  "confidence": "High",
  "cvss_score": 8.5,
  "cvss_estimated": false,
  "epss_score": 0.00205,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}