Security readout for executives and security teams
Plain-English summary
CVE-2024-49699 affects the WordPress ARPrice plugin through version 4.1.3. It can let an authenticated low-privilege user abuse unsafe deserialization, potentially leading to full confidentiality, integrity, and availability impact. Treat this as high urgency on WordPress sites where ARPrice is installed.
Executive priority
Prioritize remediation on externally reachable WordPress sites using ARPrice, especially where users can log in or self-register. The impact rating is high, but current provided evidence does not show confirmed active exploitation.
Technical view
The issue is CWE-502 deserialization of untrusted data in reputeinfosystems ARPrice. The CVSS 3.1 score is 8.8 with network attack vector, low complexity, low privileges required, and no user interaction. Sources do not provide exploit details, gadget-chain requirements, or a confirmed fixed version.
Likely exposure
Exposure is limited to WordPress installations running ARPrice version 4.1.3 or earlier. The CVSS vector indicates exploitation requires low privileges, so sites allowing user registration, contributor accounts, or compromised accounts have higher practical risk.
Exploitation context
The CVE record is not marked in KEV, and the provided sources do not claim active exploitation. Public evidence supports a high-impact authenticated vulnerability, but not unauthenticated exploitation or in-the-wild use.
Researcher notes
The source bundle has a version-label inconsistency: the CVE description says through <= 4.1.3, while the Patchstack URL text references 4.0.3. Validate affected-version boundaries against vendor or Patchstack updates before final scoping.
Mitigation direction
- Inventory WordPress sites for the ARPrice plugin and installed version.
- Review vendor and Patchstack guidance for a fixed release or official mitigation.
- Disable ARPrice where it is not business-critical until remediation is confirmed.
- Restrict low-privilege account creation and remove unnecessary WordPress users.
- Increase monitoring for suspicious authenticated activity on affected sites.
Validation and detection
- Confirm whether ARPrice is installed on each WordPress instance.
- Record the installed ARPrice version and compare it to <= 4.1.3.
- Review WordPress user roles for unnecessary low-privilege access.
- Check security logs for unusual authenticated requests to ARPrice functionality.
- Track vendor or Patchstack updates for fixed-version confirmation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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 lookupCVE-2024-49699 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9PatchstackVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/Wordpress/Plugin/arprice/vulnerability/wordpress-arprice-plugin-4-0-3-php-object-injection-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.