LiveActive security incident?Get immediate response
CVE Record

CVE-2023-33329: WordPress Custom Post Type Generator Plugin <= 2.4.2 is vulnerable to Cross Site Scripting (XSS)

Auth. (admin+) Reflected Cross-Site Scripting (XSS) vulnerability in Hijiri Custom Post Type Generator plugin <= 2.4.2 versions.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a reflected XSS issue in the Hijiri Custom Post Type Generator WordPress plugin through 2.4.2. The cited record says exploitation requires an authenticated administrator and user interaction. Business impact is usually limited, but compromise of an admin session can affect site content, settings, and trust.

Executive priority

Treat as a moderate-priority WordPress hygiene issue. It is not cited as actively exploited, but affected admin tooling should be updated, disabled, or formally accepted because administrator-session compromise can have visible business impact.

Technical view

CVE-2023-33329 is CWE-79 reflected cross-site scripting in the WordPress Custom Post Type Generator plugin <= 2.4.2. CVSS 3.1 is 5.9 with network access, low complexity, high privileges, required user interaction, and changed scope. Sources do not identify a specific parameter, fixed version, or remediation release.

Likely exposure

Exposure is limited to WordPress environments using Hijiri Custom Post Type Generator version 2.4.2 or earlier. The source indicates admin-level authentication is required, so this is not described as anonymous exploitation.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The vector requires a privileged authenticated user and interaction, reducing broad opportunistic risk but still relevant for admin-facing WordPress attack paths.

Researcher notes

Evidence is sparse. The CVE states reflected XSS in Hijiri Custom Post Type Generator <= 2.4.2, but no parameter, proof detail, fixed release, or patch note is included in the supplied bundle. Avoid assuming broader products or anonymous reach.

Mitigation direction

  • Inventory WordPress sites for the Custom Post Type Generator plugin.
  • Check whether installed versions are 2.4.2 or earlier.
  • Review vendor or Patchstack guidance for fixed versions or official mitigation.
  • Disable or remove the plugin where it is not required.
  • Limit WordPress administrator access to trusted users only.
  • Prioritize update or replacement if no maintained fixed release is available.

Validation and detection

  • Confirm plugin presence and version across WordPress assets.
  • Verify administrator-only access assumptions against local site configuration.
  • Review recent admin activity for suspicious crafted links or unexpected redirects.
  • Check vendor, CVE, and Patchstack records for remediation updates.
  • Document any exposed affected instance and its owner.
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-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-33329 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.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/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
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
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L1.73.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/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
HijiriCustom Post Type Generatorcustom-post-type-generator, n/aunaffected
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.