The plugin register. Used on 200,000+ sites

PrettyLinks

19known security flaws found in PrettyLinks
since June 2011

Safe from 3.6.21

Version 3.6.21 or later fixes all of them. A site on an older version is open to them.

Or let us look for you

Free, with no sign up. About ten seconds, and nothing on your site is touched. See an example report

When they were found.

Advisory: Database injection, June 2011Advisory: Cross-site scripting, October 2011Advisory: Cross-site scripting, December 2011Advisory: Cross-site scripting, January 2012Advisory: Cross-site scripting, May 2012Advisory: Cross-site scripting, February 2013Advisory: Cross-site scripting, March 2014Major: Database injection, July 2015Advisory: a security flaw, November 2015Advisory: a security flaw, July 2016Major: Cross-site scripting, June 2019Advisory: Cross-site scripting, June 2019Advisory: a security flaw, June 2019Minor: Forged requests, April 2023Minor: Forged requests, March 2024Major: Cross-site scripting, March 2024Advisory: Missing checks, May 2025Minor: Database injection, August 202620112013201520172019202120232025

DangerousMajorMinorAdvisory

What they could let someone do.

What could happen

  • Cross-site scripting

    Someone could make your pages run their own script in visitors' browsers, to steal logins, show a fake payment form or send people to a scam site.

    How: The software puts text it was sent back onto a page without making it safe first, so a script hidden in a link, form or comment runs as if it were part of your site.

    Read about it here
  • Database injection

    Someone could read or change what is in the site's database: customer details, orders, password records, or a new administrator account.

    How: The software builds its questions to the database out of what visitors type, so carefully written input changes the question itself.

    Read about it here
  • Forged requests

    Someone could get a signed in administrator to change something without knowing, such as adding a new admin or changing settings, just by visiting a page.

    How: The software does not check that a change came from its own pages, so another site can quietly send one through the administrator's browser.

    Read about it here
Every known flaw, newest first (19)
  1. August 2026MinorDatabase injectionFixed in 3.6.21. Needs a login on the site (Administrator+).
  2. May 2025AdvisoryMissing checksFixed in 3.6.16.
  3. March 2024MajorCross-site scriptingFixed in 3.6.3. No login needed.
  4. March 2024MinorForged requestsFixed in 3.6.4. No login needed.
  5. April 2023MinorForged requestsFixed in 3.4.1. No login needed.
  6. June 2019AdvisoryCross-site scriptingFixed in 2.1.10.
  7. June 2019AdvisoryA security flawFixed in 2.1.10.
  8. June 2019MajorCross-site scriptingFixed in 2.1.10. No login needed.
  9. July 2016AdvisoryA security flawFixed in 1.6.1.
  10. November 2015AdvisoryA security flawFixed in 1.6.8.
  11. July 2015MajorDatabase injectionFixed in 1.6.8. Needs a login on the site.
  12. March 2014AdvisoryCross-site scriptingFixed in 1.6.3.
  13. February 2013AdvisoryCross-site scriptingFixed in 1.6.4.
  14. May 2012AdvisoryCross-site scriptingFixed in 1.5.3.
  15. January 2012AdvisoryCross-site scriptingFixed in 1.5.6.
  16. December 2011AdvisoryCross-site scriptingFixed in 1.5.4.
  17. October 2011AdvisoryCross-site scriptingFixed in 1.4.6.
  18. June 2011AdvisoryDatabase injection
  19. Date not knownAdvisoryCross-site scriptingFixed in 1.6.1.

From the public lists of known flaws, checked daily. A flaw is listed once it is made public, often after a fix is out.

Be told the day a new one is found.

Mendbird checks your site every morning against the lists of known flaws, and emails you in plain English the day one hits something you run. Free for 14 days, then £9 a month.

Start my free trial