Skip to content
PluginCanary

Display Remote Posts Block

by Oliver Campion · 700+ active installs · Checked 3 Nov 2026
Healthy

Healthy: maintained, last release 14 Aug 2026, 4 releases in 24 months, no unpatched vulnerabilities.

90/ 100 Canary Score
Sub-scores for Display Remote Posts Block
Ownership100
Maintenance100
Security95
Support70
Reputation70

How the score works

Quick answers

Is Display Remote Posts Block still maintained?
Yes. Last release 14 Aug 2026, 4 releases in the last 24 months. 14 Aug 2026 · wordpress.org
Who owns Display Remote Posts Block, and has it changed hands?
No change recorded. Main committer domainsupport since Feb 2021. 3 Nov 2026 · SVN log
Was Display Remote Posts Block removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is Display Remote Posts Block safe?
1 known vulnerability, fixed (latest in 1.1.1). Not on the exploited list. 7 May 2025 · Wordfence Intelligence
Is the latest Display Remote Posts Block update safe to install?
No ownership change before 1.1.4. No one-star spike after it. 12 Jan 2026 · Release history

Active signals

Facts we detected, with links to the source.

No open risk signals. Signals appear here when we detect an ownership change, closure, vulnerability or decline.

Ownership timeline

Who commits to the plugin's code on wordpress.org, over time.

Committers and their active periods
plugin-master22 Feb 2021 to 22 Feb 2021, 1 commits
domainsupport23 Feb 2021 to 14 Aug 2026, 29 commits

2 committers recorded. No ownership change since 2021.

Maintenance

Last release
3 months ago
Releases, 24 months
4
Tested up to
7.1 current
Requires PHP
7.0 supported 8.2+
Releases per quarter
Releases per quarter for Display Remote Posts Block
Q1 20241
Q2 20241
Q3 20240
Q4 20241
Q1 20250
Q2 20252
Q3 20250
Q4 20251
Q1 20261
Q2 20260
Q3 20260
Q4 20260

Last release 14 Aug 2026. Tested with WordPress 7.1 (current).

Reputation

Last 90 days: no reviews.

Rating distribution
5 star0
4 star0
3 star0
2 star0
1 star0

Security record

1 vulnerability in 24 months, patched (latest fixed in 1.1.1).

Show 1 patched vulnerability
PublishedIssueCVSSAffectedFixed inDays to patch
7 May 2025Display Remote Posts Block <= 1.1.0 - Authenticated (Contributor+) Server-Side Request Forgery6.4<= 1.1.01.1.1n/a

Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.

Support

Support history appears after our first snapshots of the forum counts.

Momentum

700+ active installs. History builds with each weekly snapshot.

Momentum history builds with each snapshot.

Healthier alternatives

Same job, rated Healthy, higher Canary Score and at least 10,000 installs. Never sponsored.

No healthier plugin in the same category yet.

Facts

Version1.1.4
AuthorOliver Campion
Added23 Feb 2021
Last updated14 Aug 2026
Active installs700+
Requires WordPress5.0
Tested up to7.1.4
Requires PHP7.0
CategoryContent Management > Blog & Article Publishing
Tagsrss, blog, block, blogger, jetpack

Other plugins by this author: Remove "Powered by WordPress", Options for Twenty Seventeen, Options for Twenty Twenty-One, Options for Twenty Twenty, SideMenu, Options for Twenty Nineteen, Reset Customizer, Block wp-login, Options for Block Themes, Deny All Firewall, Slidey Panel, Web:D Accounts

Questions

Is Display Remote Posts Block still maintained?

Yes. Last release 14 Aug 2026, 4 releases in the last 24 months.

Who owns Display Remote Posts Block, and has it changed hands?

No change recorded. Main committer domainsupport since Feb 2021.

Was Display Remote Posts Block removed from wordpress.org?

No. Listed on wordpress.org as of 3 Nov 2026.

Is Display Remote Posts Block safe?

1 known vulnerability, fixed (latest in 1.1.1). Not on the exploited list.

Is the latest Display Remote Posts Block update safe to install?

No ownership change before 1.1.4. No one-star spike after it.

Data: wordpress.org Plugins API, plugins SVN and Trac, wordpress.org reviews and support forum, Wordfence Intelligence, CISA KEV, NVD.Plugin data refreshed 3 Nov 2026.Report a data issue