CVE-2023-49853

PayTR Taksit Tablosu <= 1.3.3 - Improper Authorization

2023-12-07 00:00
qilin_99

Strategic Overview

Status
Unpatched
Affected Version
<= 1.3.3
CVSS
5.3Medium
Weakness type
CWE-285 · Improper Authorization
CVE
CVE-2023-49853
View all PayTR Taksit Tablosu – WooCommerce vulnerabilities

At a glance

CVE-2023-49853 is a medium-severity Improper Authorization vulnerability in the PayTR Taksit Tablosu WordPress plugin, affecting versions <= 1.3.3. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed December 2023, reported by qilin_99.

Vulnerability Overview

The PayTR Taksit Tablosu plugin for WordPress is vulnerable to improper authorization in versions up to, and including, 1.3.3. This makes it possible for unauthenticated attackers to perform an unauthorized action.

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 privileges on the target site, and no interaction from a victim user.

CWE-285: Improper Authorization

Reaching this weakness in PayTR Taksit Tablosu <= 1.3.3 takes a caller who can reach the endpoint. 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. No fixed build of this plugin is recorded for PayTR Taksit Tablosu yet, so installs running <= 1.3.3 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

Related records

Other vulnerabilities in PayTR Taksit Tablosu – WooCommerce

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C