How severe is CVE-2018-3810?

No CVSS score has been assigned to CVE-2018-3810 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2018-3810?

Affected package information for CVE-2018-3810 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2018-3810?

No fixed release is recorded for CVE-2018-3810 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2018-3810 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2018-3810 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2018-3810 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2018-3810, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-3810?

CVE-2018-3810 has an EPSS (Exploit Prediction Scoring System) score of 91.3%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2018-3810?

CVE-2018-3810 is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2018-3810?

A Nuclei detection template exists for CVE-2018-3810, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2018-3810 published, and has it been updated?

CVE-2018-3810 was published on January 1, 2018 and was last updated on August 5, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2018-3810 — WordPress

CVE-2018-3810 is a Improper Authentication vulnerability. 3 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Authentication Bypass vulnerability in the Oturia Smart Google Code Inserter plugin before 3.5 for WordPress allows unauthenticated attackers to insert arbitrary JavaScript or HTML…

Published

Jan 1, 2018

Updated

Aug 5, 2024

Affected

1 product

Patched

See advisory

Exploits

3 known

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

91.3%probability of exploitation in next 30 days

Very High Risk+0.16%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

Authentication Bypass vulnerability in the Oturia Smart Google Code Inserter plugin before 3.5 for WordPress allows unauthenticated attackers to insert arbitrary JavaScript or HTML code (via the sgcgoogleanalytic parameter) that runs on all pages served by WordPress. The saveGoogleCode() function in smartgooglecode.php does not check if the current request is made by an authorized user, thus allowing any unauthenticated user to successfully update the inserted code.

Affected Products

1 product · 1 configurations

Application

smart google code inserteroturia

< 3.5

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-43420webappsphp✓ Verified

WordPress Plugin Smart Google Code Inserter < 3.5 - Authentication Bypass / SQL Injection

by Benjamin Lim · Jan 3, 2018

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2018-3810 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

How to detect CVE-2018-3810

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2018-3810 -u https://target

Template: Oturia WordPress Smart Google Code Inserter <3.5 - Authentication Bypass
Severity: critical
Impact: An attacker can bypass authentication and gain unauthorized access to the affected WordPress site.
Remediation: Update to the latest version of the Oturia WordPress Smart Google Code Inserter plugin (3.5 or higher) to fix the authentication bypass vulnerability.

Template by ProjectDiscovery nuclei-templates (princechaddha), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-3810 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works