Vulnerability report

Active exploitation observed Confirmed confidence Not in CISA KEV

CVE-2023-54359

WordPress adivaha Travel Plugin 2.3 SQL Injection

Adivaha / WordPress adivaha Travel Plugin · 2.3

Watch CVE-2023-54359 Browse KEV feed
Severity
CVSS 8.8 · High
Confidence
Confirmed
Exploit status
Observed in sensors
EPSS
0.3%
First observed
19 Jul 2026
Last observed
18 Oct 2026

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2023-54359 is an unauthenticated vulnerability affecting Adivaha WordPress adivaha Travel Plugin. WordPress adivaha Travel Plugin 2.3 contains a time-based blind SQL injection vulnerability that allows...

Is it exploited?

Yes. Previdian sensors observed exploitation attempts with confirmed confidence. Also confirmed by third-party sources.

Who is affected?

Adivaha / WordPress adivaha Travel Plugin 2.3.

What should we do?

Patch immediately, validate internet-facing exposure, and monitor for matching requests.

Overview

WordPress adivaha Travel Plugin 2.3 SQL Injection

WordPress adivaha Travel Plugin 2.3 contains a time-based blind SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the 'pid' GET parameter.

Attackers can send requests to the /mobile-app/v3/ endpoint with crafted 'pid' values using XOR-based payloads to extract sensitive database information or cause denial of service.

Adivaha Affected
WordPress adivaha Travel Plugin
2.3
View vendor advisory (opens in new tab)
Published
09 Apr 2026
Exploited Since
19 Jul 2026
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

Tags

wordpress

CVE References

Exploitation evidence

Why Previdian marks this CVE as exploited

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

Exploited in the wild

The Shadowserver

Recorded 02 Aug 2026

Previdian independently recorded this as exploited after first seeing it in honeypot sensors.

Active exploitation observed

Previdian sensor

First observed 19 Jul 2026

Previdian first observed exploitation attempts targeting this vulnerability in our honeypot sensors.

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
The Shadowserver First 2026-08-02 00:00 UTC
Previdian Sensors 2026-08-03 13:35 UTC

Operational indicators for this CVE are listed under Detection.

Sensor telemetry

First-party evidence of exploitation activity

Previdian sensors recorded exploitation attempts targeting this vulnerability. The cards and chart show volume, unique attackers, and daily activity.

3

Attempts observed

3

Unique attacker IPs

3

Attacker countries

CH · US · YE

3

Sensors observed

CVE-2023-54359 exploitation attempts over the last 30 days

Daily events observed by Previdian sensors

Updated 18 Oct 2026

0
1
0
0
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
19 Sep 25 Sep 1 Oct 7 Oct 18 Oct

First observed 19 Jul 2026 · Last observed 18 Oct 2026

Pro adds sensor region and window summaries. Enterprise adds raw IPs, paths, User-Agents, and payloads.

Start 14-day Pro trial

Detection

Operational artifacts and observed signals

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

Observed signals

Request targets
User-Agents
Callback hosts
1
3
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

Previdian virtual patch guidance is available for this CVE.

AWS WAF Cloudflare ModSecurity

Attacker IP Indicators

Attacker IP indicators observed · available in Pro and Enterprise.

Sensor-derived attacker IP indicators are available to Pro and Enterprise accounts under Detection and through the Pro API.

Learn about Pro API access

Virtual Patch Detail

Compensating WAF rules for this CVE.

Available

Enterprise feature. Virtual patch rule content and deployable vendor exports (ModSecurity, Cloudflare, AWS WAF) are available to Previdian Enterprise users.

Talk to Sales Learn About Virtual Patches

Risk and context

Severity, weaknesses, and research context

CVSS v4.0

8.8 High

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

EPSS

0.3%

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

All CVSS Scores

CVSS v4.0 8.8 High

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

CVSS v3.1 8.2 High

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

Timeline

From disclosure to observed exploitation

  1. 11:35 UTC

    Virtual patch available

    Compensating WAF rule available to block exploitation

  2. 00:00 UTC

    Added to Previdian KEV Feed

    High-confidence, third-party attested exploitation

  3. 02:14 UTC

    Indicators of compromise added (4)

    Indicators of compromise recorded

  4. 02:14 UTC

    Observed by Previdian sensors

    Evidence-backed exploitation signal

  5. 20:54 UTC

    CVE published

    Vulnerability disclosed publicly

  6. 20:41 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-2023-54359

Sample API response 
{
  "cve_id": "CVE-2023-54359",
  "confidence": "Confirmed",
  "cvss_score": 8.8,
  "cvss_estimated": false,
  "epss_score": 0.00269,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": true
  },
  "sensor_telemetry": { "attempts": 3, "sensors": 3 }
}