Skip to content
Founder-led WordPress incident response and care Request an assessment
3zerodigital Request a Website Assessment

Plugin security history

FG Joomla to WordPress Vulnerability History & Security Timeline

The Wordfence Intelligence dataset currently contains 3 vulnerability records associated with FG Joomla to WordPress, published between 2017 and 2024.

Dataset last synchronized: 2026-08-03 00:31:25 UTC

At a glance

Security Snapshot

3Total records
0Critical
1High
2Medium
0Low
0Informational
3Patched records
0Currently marked unpatched
2017-08-24First disclosure
2024-04-22Latest disclosure
2 of 3CVE coverage

Use this history

Check and watch FG Joomla to WordPress.

A history record does not establish whether the version installed on your website is affected. Enter the exact version in the checker, or add this software to a private Critical/High alert watchlist.

Year-by-Year Timeline

YearRecordsRelative volume
201711 records
202422 records

Severity Breakdown

SeverityRecordsShare
High133.3%
Medium266.7%

Vulnerability-Type Breakdown

Cross-Site Scripting

1 record33.3%

First: 2017. Latest: 2017.

CSRF

1 record33.3%

First: 2024. Latest: 2024.

Information Disclosure

1 record33.3%

First: 2024. Latest: 2024.

Patch Status

Patched
3
Currently marked unpatched
0
Unknown status
0

Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.

Latest Known Patched Versions

  • 4.21.0
  • 4.17.0
  • 3.31.0

Affected-Version History

Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.

Affected rangeVulnerabilityPublishedPatched versionSeverity
*-4.20.2FG Joomla to WordPress <= 4.20.2 - Sensitive Information ExposureApril 22, 20244.21.0Medium
*-4.15.0FG Drupal to WordPress <= 3.67.0 - Cross-Site Request Forgery via ajax_importerFebruary 2, 20244.17.0Medium
[*, 3.31.0)FG Joomla to WordPress < 3.31.0 - Authenticated Stored Cross-Site ScriptingAugust 24, 20173.31.0High

Selected source records

Latest Records

MediumCVE-2024-32788

FG Joomla to WordPress <= 4.20.2 - Sensitive Information Exposure

Published: April 22, 2024

Affected versions
*-4.20.2
Patched versions
4.21.0
Original Wordfence record
MediumCVE-2024-24837

FG Drupal to WordPress <= 3.67.0 - Cross-Site Request Forgery via ajax_importer

Published: February 2, 2024

Affected versions
*-4.15.0
Patched versions
4.17.0
Affected versions
*-4.44.3
Patched versions
4.45.0
Affected versions
*-3.67.0
Patched versions
3.68.0
Original Wordfence record
High

FG Joomla to WordPress < 3.31.0 - Authenticated Stored Cross-Site Scripting

Published: August 24, 2017

Affected versions
[*, 3.31.0)
Patched versions
3.31.0
Original Wordfence record

Highest-Severity Records

High

FG Joomla to WordPress < 3.31.0 - Authenticated Stored Cross-Site Scripting

Published: August 24, 2017

Affected versions
[*, 3.31.0)
Patched versions
3.31.0
Original Wordfence record
MediumCVE-2024-32788

FG Joomla to WordPress <= 4.20.2 - Sensitive Information Exposure

Published: April 22, 2024

Affected versions
*-4.20.2
Patched versions
4.21.0
Original Wordfence record
MediumCVE-2024-24837

FG Drupal to WordPress <= 3.67.0 - Cross-Site Request Forgery via ajax_importer

Published: February 2, 2024

Affected versions
*-4.15.0
Patched versions
4.17.0
Affected versions
*-4.44.3
Patched versions
4.45.0
Affected versions
*-3.67.0
Patched versions
3.68.0
Original Wordfence record

View all associated vulnerabilities

Need help reviewing an exposed WordPress website?

Running an affected version does not prove that a website was compromised. Suspicious redirects, unknown administrators, injected content, unexpected files or recurring malware may require a manual investigation.

Vulnerability data: Wordfence Intelligence. Analysis and practical guidance: 3Zero Digital.

Data Source, Attribution and Methodology

This page aggregates active Production Feed records. Counts are not software-quality rankings, and an affected version does not prove exploitation or infection. Read the full methodology.

Return to the Security History Directory