CVE-2017-20208: Metagauss Registrationmagic insecure deserialization (CVSS 9.8)

Description

The RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login plugin for WordPress is vulnerable to PHP Object Injection in all versions up to 3.7.9.3 (exclusive) via deserialization of untrusted input from the is_expired_by_date() function. This makes it possible for unauthenticated attackers to inject a PHP Object. The additional presence of a POP chain allows attackers to fetch a remote file and install it on the site.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Metagauss Registrationmagic< 3.7.9.3

Remediation

Fixed in

Metagauss Registrationmagic≥ 3.7.9.3

Patch & vendor advisories

https://plugins.trac.wordpress.org/changeset/1733274/custom-registration-form-builder-with-submission-manager

References

https://plugins.trac.wordpress.org/changeset/1733274/custom-registration-form-builder-with-submission-managerPatch
https://www.wordfence.com/blog/2017/10/3-zero-day-plugin-vulnerabilities-exploited-wild/Press/Media CoverageThird Party Advisory
https://www.wordfence.com/threat-intel/vulnerabilities/id/c2b79193-f8fc-4ea2-8973-fe292cfb926b?source=cveTechnical Description

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2017-20208 being actively exploited?

CVE-2017-20208 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.71%.

How severe is CVE-2017-20208?

CVE-2017-20208 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.71% probability of exploitation.

Which products are affected by CVE-2017-20208?

Affected products include Metagauss Registrationmagic.

How do I fix CVE-2017-20208?

Upgrade affected software to a fixed version, for example Metagauss Registrationmagic 3.7.9.3 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2017-20208 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo