LiveActive security incident?Get immediate response
CVE Record

CVE-2022-44591: WordPress Anthologize plugin <= 0.8.0 - Auth. Stored Cross-Site Scripting (XSS) vulnerability

Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in Anthologize plugin <= 0.8.0 on WordPress.

MediumCVSS 4.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-44591 is a stored cross-site scripting issue in the WordPress Anthologize plugin through version 0.8.0. It requires an authenticated administrator-level user, so it is not a broad unauthenticated internet attack. The main business concern is abuse of a compromised admin account to affect other users in the WordPress admin context.

Executive priority

Handle during the normal vulnerability remediation cycle, with faster action on externally exposed WordPress sites or environments with weak admin controls. The issue is moderate because exploitation requires high privileges, but it can still matter if admin credentials are compromised.

Technical view

The issue is CWE-79 stored XSS in Anthologize <= 0.8.0 for WordPress. CVSS 3.1 is 4.8 with network access, low complexity, high privileges, user interaction required, changed scope, low confidentiality impact, low integrity impact, and no availability impact.

Likely exposure

Exposure is limited to WordPress sites running the Anthologize plugin at version 0.8.0 or earlier. Risk is highest where WordPress admin accounts are shared, weakly protected, or already compromised. The source bundle does not identify affected CPEs or downstream bundled products.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates exploitation requires administrator-level privileges and user interaction. Treat this as a targeted post-authentication web risk, not confirmed mass exploitation.

Researcher notes

Evidence is limited to the CVE metadata and Patchstack reference in the bundle. Do not assume a public exploit, active exploitation, or a specific fixed version from these sources alone. Validation should focus on plugin presence, version, admin control strength, and vendor guidance.

Mitigation direction

  • Inventory WordPress sites for the Anthologize plugin and record versions.
  • Check vendor, CVE, and Patchstack guidance for an available fixed version or official workaround.
  • Disable or remove Anthologize where it is not business-critical.
  • Restrict WordPress administrator access and enforce strong authentication controls.
  • Review recent administrator account activity for suspicious content changes.

Validation and detection

  • Confirm whether Anthologize is installed on each WordPress site.
  • Verify installed versions and flag anything at or below 0.8.0.
  • Check whether administrator accounts are protected by MFA and least privilege.
  • Review plugin-managed content or settings for unexpected script-like changes.
  • Document whether vendor remediation guidance is available for your environment.
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-2022-44591 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.8 (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: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.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N1.72.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.8Medium
CVSS 3.1 vector shape for CVE-2022-44591Attack 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: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
One Week | One ToolAnthologize (WordPress plugin)<= 0.8.0Listed
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.