LiveActive security incident?Get immediate response
CVE Record

CVE-2024-24866: WordPress Biteship Plugin <= 2.2.24 is vulnerable to Cross Site Scripting (XSS)

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Biteship Biteship: Plugin Ongkos Kirim Kurir Instant, Reguler, Kargo allows Reflected XSS.This issue affects Biteship: Plugin Ongkos Kirim Kurir Instant, Reguler, Kargo: from n/a through 2.2.24.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-24866 is a reflected cross-site scripting issue in the WordPress Biteship shipping plugin through version 2.2.24. An attacker may be able to lure a user into opening a malicious link that causes script to run in the victim's browser. The source bundle does not show active exploitation.

Executive priority

Treat this as a high-priority web application exposure if your business uses the Biteship WordPress shipping plugin. The main risk is browser-based compromise of users or administrators after interaction with a malicious link, not confirmed mass exploitation.

Technical view

The issue is CWE-79 improper neutralization during web page generation in Biteship: Plugin Ongkos Kirim Kurir Instant, Reguler, Kargo. CVSS 3.1 is 7.1 with network access, low complexity, no privileges, required user interaction, and changed scope. Affected versions are reported through 2.2.24.

Likely exposure

Exposure is limited to WordPress sites using the Biteship plugin at version 2.2.24 or earlier. Sites not using this plugin are not indicated as affected in the source bundle.

Exploitation context

The CVE and Patchstack reference describe reflected XSS, which typically requires a victim to interact with a crafted link or request. CISA KEV status is false in the bundle, so active exploitation is not established here.

Researcher notes

The source bundle does not include a fixed version, vulnerable parameter, proof of concept, or exploit telemetry. Validation should stay non-invasive: identify plugin presence and version, then align remediation with vendor or Patchstack guidance.

Mitigation direction

  • Inventory WordPress sites for the Biteship plugin and record installed versions.
  • Check Biteship, WordPress.org, or Patchstack guidance for a fixed release or workaround.
  • Prioritize remediation for public sites and administrator-facing workflows using the plugin.
  • If no supported fix exists, assess disabling or replacing the plugin based on business need.

Validation and detection

  • Confirm whether any site runs Biteship version 2.2.24 or earlier.
  • Verify remediation by checking the plugin version or confirming removal from WordPress.
  • Review vendor advisories before assuming a patched version is available.
  • Check web and WordPress logs for unusual links targeting Biteship-related pages.
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-2024-24866 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
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2024-24866Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
BiteshipBiteship: Plugin Ongkos Kirim Kurir Instant, Reguler, Kargobiteship, 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.