CVE-2024-50548: WordPress Awesome Progress Bar plugin <= 1.0.13 - Cross Site Scripting (XSS) vulnerability
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Abdullah Nahian Awesome Progress Bar awesome-progess-bar allows DOM-Based XSS.This issue affects Awesome Progress Bar: from n/a through <= 1.0.13.
Security readout for executives and security teams
Plain-English summary
CVE-2024-50548 is a DOM-based cross-site scripting issue in the WordPress Awesome Progress Bar plugin. A logged-in attacker could potentially cause script execution when another user interacts with crafted content or pages. The business risk is moderate and mainly affects sites using this plugin through version 1.0.13.
Executive priority
Treat as a scheduled but prompt WordPress hygiene item. Prioritize public-facing sites, sites with many content contributors, and environments handling sensitive user sessions. There is no supplied evidence of active exploitation, but XSS can support account abuse and data exposure.
Technical view
The CVE describes improper input neutralization during web page generation, classified as CWE-79. Scope is changed, with network access, low attack complexity, low privileges required, and user interaction required. CVSS 3.1 score is 6.5. Public data identifies Awesome Progress Bar package `awesome-progess-bar` as affected through version 1.0.13.
Likely exposure
Exposure is likely limited to WordPress sites with the Awesome Progress Bar plugin installed, especially versions up to 1.0.13. The source bundle does not identify broader platform exposure or affected forks.
Exploitation context
The CVE and Patchstack entry describe DOM-based XSS. The CVSS vector requires low privileges and user interaction. CISA KEV status is false in the supplied data, and no cited source here confirms active exploitation.
Researcher notes
Evidence is limited to the CVE record and Patchstack reference. The source bundle does not provide exploit details, a fixed version, or vendor advisory text. Note the package spelling `awesome-progess-bar` and the version inconsistency in provided affected metadata versus the description.
Mitigation direction
Inventory WordPress sites for the Awesome Progress Bar plugin.
Identify installed plugin versions and compare against affected versions through 1.0.13.
Check Patchstack and the plugin vendor for current remediation guidance.
Disable or remove the plugin if it is unused or cannot be remediated.
Apply an available vendor update if one is published and tested.
Validation and detection
Confirm whether `awesome-progess-bar` is installed on each WordPress instance.
Record the plugin version from WordPress administration or asset inventory.
Review user roles able to create or modify plugin-related content.
Check web logs for unusual authenticated activity around affected pages.
Retest after remediation using approved non-destructive security validation.
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.
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.
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.
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.