Security readout for executives and security teams
Plain-English summary
RegistrationMagic versions through 6.0.9.7 reportedly allow an unauthenticated internet user to submit data that PHP may interpret as an object. The supplied CVSS assessment indicates possible complete compromise of confidentiality, integrity, and availability. Actual impact may depend on exploitable code already present on the WordPress site.
Executive priority
Treat as an urgent asset-identification and remediation task because exploitation requires no authentication and the assessed impact is critical. Prioritize public WordPress sites first. Do not claim compromise solely from exposure; investigate logs and endpoint activity, while obtaining definitive upgrade guidance from the vendor or cited advisory.
Technical view
CVE-2026-73341 is classified as CWE-502, deserialization of untrusted data, affecting the RegistrationMagic WordPress plugin through 6.0.9.7. The attack is network-accessible, low complexity, requires no privileges or user interaction, and has a CVSS 3.1 score of 9.8. The supplied sources do not identify the vulnerable endpoint, prerequisite gadget chain, or corrected version.
Likely exposure
Internet-facing WordPress installations using RegistrationMagic 6.0.9.7 or earlier are the likely exposure. Inventory certainty is limited because the structured affected entry lists versions as “n/a” and default status as “unaffected,” conflicting with the title and description. Confirm installed versions and vendor guidance directly.
Exploitation context
The supplied bundle does not establish active exploitation, and the CVE is not listed as KEV in the provided data. PHP object injection can have severe consequences when a usable gadget chain exists, but the sources supplied here do not document exploit prerequisites, observed attacks, or demonstrated outcomes.
Researcher notes
The public bundle supports the vulnerability class, affected-version ceiling, and CVSS vector, but provides no endpoint, root-cause detail, gadget-chain requirements, proof of exploitation, or fixed release. The contradictory structured affected status warrants caution. Testing should remain defensive and authorized, focusing on version confirmation, reachability, telemetry, and vendor-supported remediation.
Mitigation direction
- Identify every WordPress site running RegistrationMagic and record its installed version.
- Check current Metagauss and Patchstack guidance for a confirmed corrected version or mitigation.
- Update to a vendor-confirmed safe release when one is identified.
- Disable or remove the plugin temporarily where exposure cannot be resolved promptly.
- Restrict unnecessary public access and strengthen monitoring until remediation is confirmed.
Validation and detection
- Verify plugin versions from authoritative WordPress administration or asset inventory records.
- Confirm whether RegistrationMagic endpoints are reachable without authentication.
- Review web, application, and security logs for anomalous requests targeting plugin functionality.
- Confirm the deployed release against current vendor and Patchstack advisories.
- After remediation, verify the vulnerable version is absent across production and recovery environments.
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-2026-73341 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
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/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:N/UI:N/S:U/C:H/I:H/A:H3.95.9PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/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
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.