LiveActive security incident?Get immediate response
CVE Record

CVE-2023-3053: Page Builder by AZEXO <= 1.27.133 - Missing Authorization to Post Creation

The Page Builder by AZEXO plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'azh_add_post' function in versions up to, and including, 1.27.133. This makes it possible for authenticated attackers to create a post with any post type and post status.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A logged-in user could abuse the Page Builder by AZEXO WordPress plugin to create posts they should not be allowed to create. The issue is business-relevant where many users can authenticate, because it can affect site content integrity and operations.

Executive priority

Treat as a moderate-priority WordPress hygiene issue. It is not reported as actively exploited in the provided sources, but it can allow unauthorized content changes on affected sites with user accounts.

Technical view

CVE-2023-3053 is a missing authorization check, CWE-862, in the plugin's azh_add_post function. Sources describe Page Builder by AZEXO versions up to and including 1.27.133 as allowing authenticated attackers to create posts with any post type and status. CVSS is 5.4.

Likely exposure

Exposure is limited to WordPress sites running Page Builder by AZEXO at versions up to 1.27.133 and allowing authenticated users. Public-only sites without user accounts have lower practical exposure, but administrator accounts should still verify plugin presence and version.

Exploitation context

The provided bundle does not show CISA KEV listing or other evidence of active exploitation. The attack requires authentication and low complexity, with no user interaction. Impact is unauthorized data modification through post creation, not disclosed credential theft or remote code execution.

Researcher notes

The affected metadata in the bundle is sparse, while the description and Wordfence reference provide the vulnerable range. Validate against the Wordfence advisory and plugin source references. Do not assume unauthenticated exploitation or a specific patch unless vendor guidance confirms it.

Mitigation direction

  • Inventory WordPress sites for Page Builder by AZEXO plugin usage.
  • Check whether installed versions are up to and including 1.27.133.
  • Review Wordfence and vendor plugin guidance for fixed versions or official remediation.
  • Update if an official fixed version is available from trusted sources.
  • Disable or remove the plugin where it is not required.
  • Limit unnecessary WordPress user accounts and permissions.

Validation and detection

  • Confirm plugin name and version on each WordPress instance.
  • Review roles with authenticated access to affected sites.
  • Check content for unexpected posts, post types, or publication statuses.
  • Review application logs for unusual post creation activity.
  • Verify remediation against vendor or Wordfence guidance.
Prepared
Confidence
medium
Sources
5

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-3053 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
5.4 (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:L

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
3Source 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
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-3053Attack 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:L

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
azexoPage Builder with Image Map by AZEXO0unaffected
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.