Summary
CVE-2025-15485 is a missing authorization (CWE-862) vulnerability in the Auto x LINE WordPress plugin, affecting all versions through 1.0.0. Several of the plugin’s REST API endpoints fail to enforce authorization checks, allowing completely unauthenticated attackers to modify plugin settings, create fraudulent entries, and clear or access activity logs. The flaw carries a CVSS v3.1 base score of 8.2 (High) and is remotely exploitable with low attack complexity and no user interaction.
Technical details
- Root cause: The plugin registers REST API endpoints without validating that the calling user is authenticated or holds sufficient capabilities before performing sensitive operations.
- Trigger conditions: An attacker simply needs network access to a WordPress site running the vulnerable plugin; no credentials or prior access are required.
- Attack vector: Network (remote), via direct HTTP requests to the plugin’s exposed REST endpoints.
- Impact: Unauthenticated actors can modify plugin configuration/settings, create bogus LINE account entries, and clear or read the plugin’s activity logs — enabling tampering with plugin behavior, destruction of audit evidence, and potential information disclosure. The CVSS vector (C:H/I:L/A:N) reflects a primary impact on confidentiality, with limited integrity impact and no direct availability impact.
Affected software
- Auto x LINE WordPress plugin — all versions from 0 through 1.0.0 (i.e., ≤ 1.0.0)
Severity
- CVSS v3.1 Base Score: 8.2 (High)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Mitigation and recommended actions
- Immediate: As of this writing, no patched version has been released by the plugin vendor. Security teams should treat this as an unresolved, actively exploitable weakness.
- Recommended actions in the absence of a patch:
- Deactivate and remove the Auto x LINE plugin from production WordPress sites until a fixed version is published.
- If the plugin must remain active, restrict access to its REST API routes at the web server or WAF layer (e.g., block or require authentication for the plugin’s
/wp-json/namespace endpoints). - Monitor WordPress REST API access logs for unexpected requests to Auto x LINE endpoints, and review plugin settings/logs for signs of tampering.
- Subscribe to vendor/plugin repository update notifications and apply an official fix immediately once one becomes available.

