Security readout for executives and security teams
Plain-English summary
Better Search Replace for WordPress exposed sites to unsafe handling of untrusted data through PHP deserialization in versions up to 1.4.4. By itself, the plugin reportedly lacks the extra gadget chain needed for full impact, but another installed plugin or theme could supply that path.
Executive priority
Treat as a high-priority WordPress hygiene issue, especially on externally reachable sites with many plugins. Prioritize update or removal, then validate broader plugin and theme exposure before considering the risk closed.
Technical view
CVE-2023-6933 is a CWE-502 PHP object injection issue in Better Search Replace <=1.4.4. The CVSS 3.1 score is 8.8. Sources state unauthenticated attackers can inject PHP objects, with higher impact possible only if another installed component provides a usable POP chain.
Likely exposure
Public WordPress sites using Better Search Replace version 1.4.4 or older are the relevant exposure group. Risk depends on the surrounding plugin and theme ecosystem because the vulnerable plugin itself reportedly has no POP chain.
Exploitation context
The bundle does not cite CISA KEV listing or active exploitation. The issue is remotely reachable and unauthenticated, but the stated CVSS vector includes user interaction and practical impact depends on an additional POP chain.
Researcher notes
The key nuance is conditional exploitability. Sources identify unauthenticated PHP object injection, but also state no POP chain exists in Better Search Replace itself. Do not assume file deletion, data theft, or code execution unless another installed component provides the chain.
Mitigation direction
- Upgrade Better Search Replace to a version newer than 1.4.4 from official vendor channels.
- If immediate upgrade is unavailable, disable or remove the plugin until vendor guidance is applied.
- Review other installed plugins and themes for known unsafe deserialization gadget chains.
- Keep WordPress, themes, and plugins current to reduce reachable POP-chain risk.
Validation and detection
- Inventory WordPress sites for Better Search Replace installations and recorded plugin versions.
- Confirm no production site is running Better Search Replace 1.4.4 or older.
- Review vendor and Wordfence advisories for fixed-version details and any updated guidance.
- Check recent web and application logs for unexpected requests targeting the plugin.
- Assess installed plugins and themes for known PHP object injection or POP-chain exposure.
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-2023-6933 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:N/UI:R/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.
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:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/895f2db1-a2ed-4a17-a4f6-cd13ee8f84af?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/better-search-replace/trunk/includes/class-bsr-db.php#L334CVE reference
- https://plugins.trac.wordpress.org/changeset/3023674/better-search-replace/trunk/includes/class-bsr-db.phpCVE reference
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.