Originality.ai AI Checker <= 1.0.15 - Missing Authorization to Authenticated (Subscriber+) Scan Log Deletion via ' ai_scan_result_remove'
Strategic Overview
- Status
- Patched in 1.0.16
- Affected Plugin
- Originality.ai AI Checker
- Affected Version
<= 1.0.15- CVSS
- 4.3Medium
- Weakness type
- CWE-285 · Improper Authorization
- CVE
CVE-2025-10902
At a glance
CVE-2025-10902 is a medium-severity Improper Authorization vulnerability in the Originality.ai AI Checker WordPress plugin, affecting versions <= 1.0.15. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.0.16; sites on affected versions should update now. Disclosed October 2025, reported by Jonas Benjamin Friedli.
Vulnerability Overview
The Originality.ai AI Checker plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'ai_scan_result_remove' function in all versions up to, and including, 1.0.15. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete all data in the wp_originalityai_log database table, which can include post titles, scan scores, credits used, and other data.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-285: Improper Authorization
Originality.ai AI Checker <= 1.0.15 carries this weakness at ai_scan_result_remove, and reaching it takes an account at Subscriber level or above. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.
A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For Originality.ai AI Checker the fix is 1.0.16: builds <= 1.0.15 are affected, anything from 1.0.16 onward is not.
Remediation
Update to version 1.0.16, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Originality.ai AI Checker 1.0.16 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Originality.ai AI Checker
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C