Vulnerability report

Trusted Third Party Report High Confidence Not in CISA KEV

CVE-2022-0867

ARPrice Lite < 3.6.1 - Unauthenticated SQLi

ARPrice Lite · affected before 3.6.1

Severity
CVSS 9.8 · Critical
Confidence
High
Exploit status
Trusted Third Party Report
EPSS
13.5%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2022-0867 is an unauthenticated ARPrice Lite < 3.6.1 - Unauthenticated SQLi.

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?

ARPrice Lite affected before 3.6.1.

What should we do?

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

Overview

ARPrice Lite < 3.6.1 - Unauthenticated SQLi

The Pricing Table WordPress plugin before 3.6.1 fails to properly sanitize and escape user supplied POST data before it is being interpolated in an SQL statement and then executed via an AJAX action available to unauthenticated users

Unknown Affected
Pricing Table Plugin
Before 3.6.1
Published
16 May 2022
Exploitation Attempts Reported
07 Jun 2025
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

Tags

nuclei_scanner

CVE References

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

The Shadowserver

Recorded 07 Jun 2025

A trusted third party reported exploitation attempts.

Proof of concept available

Nuclei Templates

Recorded 12 Jun 2026

Public scanner or PoC coverage increases practical exploitability.

Known exploited vulnerability sources

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

Request a Demo
Source Added
The Shadowserver First 2025-06-07 00:00 UTC

Detection

Operational artifacts and observed signals

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

Virtual patch status

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

Learn about virtual patches →

Scanner Artifacts

Scanner and exploit-framework references linked to this CVE.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

9.8 Critical

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

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

EPSS

13.5%

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

All CVSS Scores

CVSS v3.1 9.8 Critical

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

CVSS v2.0 7.5 High

AV:N/AC:L/Au:N/C:P/I:P/A:P

Potential Proof of Concepts

These PoCs are unverified and could contain malware. Use at your own risk.

Timeline

From disclosure to observed exploitation attempts

  1. 14:20 UTC

    Public PoC available

    Public proof-of-concept code published

  2. 00:00 UTC

    Added to Previdian KEV Feed

    High-confidence, third-party report of exploitation attempts

  3. 00:00 UTC

    Nuclei template available

    Scanner coverage available

  4. 14:30 UTC

    CVE published

    Vulnerability disclosed publicly

  5. 00:00 UTC

    CVE ID reserved

    Identifier reserved by the CNA

API

Automate this intelligence

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

  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/enterprise/kevs/CVE-2022-0867

Sample API response
{
  "cve_id": "CVE-2022-0867",
  "confidence": "High",
  "cvss_score": 9.8,
  "cvss_estimated": false,
  "epss_score": 0.1345,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}