Skip to main content

Auto x LINE Plugin EUVDEUVD-2025-210830

| CVE-2025-15485 HIGH
Missing Authorization (CWE-862)
2026-09-02 WPScan GHSA-c47c-7wwv-x7m2
8.2
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify WordPress site running Auto x LINE
  2. Delivery
    Send unauthenticated HTTP request to unprotected REST endpoint
  3. Exploit
    Read plugin settings containing LINE API credentials
  4. Execution
    Optionally overwrite settings to redirect LINE channel
  5. Impact
    Clear access logs to cover activity

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

No special conditions - remote unauthenticated exploitation against any WordPress installation running the Auto x LINE plugin through version 1.0.0 with the plugin active. The WordPress REST API is enabled by default in all modern WordPress installations (4.7+), so no non-default configuration is required. The limiting factor is plugin adoption: only sites that have installed this specific LINE integration plugin are at risk. Exploitation is constrained to the impact scope of the plugin's stored credentials and log data - it does not directly grant wp-admin access or arbitrary file write, but LINE API credential theft may enable secondary attacks against the site's LINE channel.

Impact

The CVSS 8.2 score is supported by the attack profile: fully unauthenticated, network-reachable, low-complexity exploitation against a REST endpoint - no special conditions beyond the plugin being active. The C:H rating is credible given LINE API credentials stored in plugin settings. A publicly available PoC from WPScan raises real exploitation likelihood on any unpatched instance exposed to the internet. EPSS data was not provided, so exploitation probability cannot be quantitatively compared. No CISA KEV listing means confirmed mass exploitation is not yet observed, but the combination of PoC + unauthenticated REST exposure + credential theft potential makes this a prioritized remediation item for any site running this plugin. The I:L score may understate the integrity impact - an attacker who overwrites the LINE channel token can silently redirect all LINE-sourced messages to their own channel.

Exploit ScenarioDerived

An unauthenticated attacker sends crafted HTTP GET or POST requests directly to the plugin's unprotected REST endpoints on any public WordPress site running Auto x LINE ≤1.0.0. The attacker first calls the settings-read endpoint to harvest the LINE channel access token and secret, then optionally calls the settings-write endpoint to substitute their own LINE credentials, silently redirecting all LINE communications through their controlled channel. A publicly available PoC from WPScan makes this attack trivially scriptable with no specialized tooling.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 02, 2026

Missing authorization on REST API endpoints in the Auto x LINE WordPress plugin (through version 1.0.0) allows unauthenticated remote attackers to read and modify plugin settings and erase log data. The plugin facilitates LINE messaging integration for WordPress sites, meaning exposed settings likely include LINE API credentials and channel tokens. A publicly available proof-of-concept exists per WPScan, and the unauthenticated network-accessible nature of the flaw (PR:N, AV:N) makes it trivially exploitable against any exposed instance. No actively exploited status confirmed in CISA KEV at time of analysis.

RemediationAI

No vendor-released patched version is identified in the available data - the WPScan advisory does not cite a fixed release, and the plugin version ceiling is stated as 'through 1.0.0.' Administrators should immediately deactivate and remove the plugin until a patched version is released or authorization checks are confirmed added by the developer. As a compensating control, restrict access to WordPress REST API routes at the web server or WAF layer (e.g., block external requests to /wp-json/ paths associated with this plugin) - note this may disrupt legitimate plugin functionality. Monitor the WPScan advisory at https://wpscan.com/vulnerability/3e9da619-bce1-49b5-aa35-dce22b72f9e6/ and the WordPress plugin repository for an updated release. If the plugin must remain active, rotate LINE channel access tokens and secrets immediately to limit the window of credential exposure.

Affected VersionsENISA

Auto x LINE 0 ≤1.0.0

Affected Packages

euvd auto_x_line no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The Auto x LINE plugin (CPE: cpe:2.3:a:unknown:auto_x_line:*:*:*:*:*:*:*:*) integrates WordPress with the LINE messaging platform API. It registers WordPress REST API endpoints that lack proper capability checks - the WordPress standard being current_user_can() guards on register_rest_route() callbacks. Without these checks, any unauthenticated HTTP client can invoke the endpoints directly. The root cause aligns with CWE-862 (Missing Authorization), though NVD has left CWE unassigned. The CVSS C:H signal implies that plugin settings surfaced via these endpoints likely include sensitive LINE channel credentials (channel access tokens, channel secrets) that would give an attacker control over the site's LINE integration. The I:L metric reflects the ability to overwrite settings or clear audit logs.

Know when Auto X Line gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 8.2 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
vuln.today AI 8.2 HIGH

Unauthenticated REST endpoint, network-reachable by default; C:H for likely credential exposure; I:L for settings overwrite; A:N as no service disruption described.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

DescriptionCVE.org

The Auto x LINE WordPress plugin through 1.0.0 does not have authorization checks in some of its REST endpoints, allowing unauthenticated users to call them and update the plugin settings, clear logs etc

Technical POC Analysis

The Auto x LINE plugin registers custom WordPress REST API routes under the autoxline/v1 namespace.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

The Auto x LINE WordPress plugin (versions through 1.0.0) contains a critical missing authorization flaw allowing unauthenticated remote attackers to read and modify plugin settings, including LINE API credentials and channel tokens, as well as erase audit logs. Publicly available exploit code exists, making this trivially exploitable against any exposed WordPress instance. Organizations using this plugin face immediate risk of credential theft and unauthorized LINE account compromise.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Deactivate the plugin entirely if operational impact permits; (2) Implement WAF or API gateway rules to restrict REST API access to authenticated users only; (3) Revoke and regenerate all LINE API credentials and channel tokens immediately; (4) Enable enhanced monitoring on LINE account activity to detect unauthorized API calls; (5) Audit and review access logs for REST endpoints targeted by this vulnerability to identify potential exploitation attempts.

Threat Intelligence Overview

EPSS Score
0.2%
Top 90% exploitable
Prevalence
Low
niche LINE-messaging WordPress integration with limited adoption
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

61
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +41
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy