LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47523: WordPress Auto Tag Creator plugin <= 1.0.2 - Broken Access Control vulnerability

Missing Authorization vulnerability in Ecreate Infotech Auto Tag Creator allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Auto Tag Creator: from n/a through 1.0.2.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Auto Tag Creator for WordPress has a broken access control issue through version 1.0.2. A logged-in user may be able to perform actions that should require stronger authorization, creating limited integrity risk. The supplied sources do not identify data theft, site takeover, or a confirmed fix.

Executive priority

Address in the next regular WordPress maintenance cycle unless the site allows many untrusted logins. For public membership or multi-author sites, prioritize sooner because authenticated access is part of the attack condition.

Technical view

CVE-2023-47523 is a CWE-862 missing authorization flaw in Ecreate Infotech Auto Tag Creator. CVSS 3.1 is 4.3: network reachable, low complexity, low privileges required, no user interaction, unchanged scope, and low integrity impact only.

Likely exposure

WordPress sites running the Auto Tag Creator plugin version 1.0.2 or earlier are the relevant exposure. Risk is higher where untrusted or lightly governed authenticated users can access the site.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not state active exploitation or public exploit availability. The flaw requires some authenticated access, which reduces internet-wide risk but still matters for membership, contributor, or customer-facing WordPress environments.

Researcher notes

Available evidence is sparse. The sources identify missing authorization and affected versions through 1.0.2, but do not describe the vulnerable endpoint, exact capability check, exploit pattern, or patch version. Avoid assuming broader impact beyond low integrity effects.

Mitigation direction

  • Inventory WordPress sites for Auto Tag Creator and record installed versions.
  • Check vendor and Patchstack guidance for a fixed version or recommended mitigation.
  • Update the plugin if a vendor-supported fixed release is available.
  • Disable or remove the plugin where it is not business-critical.
  • Review and minimize WordPress accounts with low-privilege access.

Validation and detection

  • Confirm whether Auto Tag Creator is installed and whether version is 1.0.2 or earlier.
  • Review WordPress users and roles for unnecessary authenticated access.
  • Check site change history for unexpected tag or plugin-related modifications.
  • Verify remediation by confirming the plugin is updated, disabled, or removed.
  • Track the CVE and Patchstack entry for updated fix information.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-47523 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2023-47523Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Ecreate InfotechAuto Tag Creatorauto-tag-creator, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.