Critical security advisoryCriticalFlagged by our vulnerability database: A flaw in WordPress’s own updater is being exploited. Sites need 7.1.4. See if your site is affectedFlagged by our vulnerability database: WordPress updater flaw is being exploited. DetailsExploited: WordPress 7.1.4. Check your site
HuttenlocherTechnologies
Updated 4 h ago

Vulnerability database

Every flaw the U.S. government’s cybersecurity agency (CISA) has confirmed attackers are using, plus the new WordPress plugin and theme bugs published each day, sorted by what they mean for a small business. We refresh it twice a day. If you see something your website or office runs, tell us.

1,781exploited flaws on CISA’s list
35added in the last 30 days
413new WordPress flaws this week
399,200entries in the database

24,771 results · page 496 of 496

  • Sep 12, 2006index.php in SpoonLabs Vivvo Article Management CMS: PHP remote file inclusionCVE-2006-4714 · WordPress plugins & themes · reported by MITREMedium 5.1

    PHP remote file inclusion vulnerability in index.php in SpoonLabs Vivvo Article Management CMS (aka phpWordPress) 3.2 and earlier, when register_globals is enabled, allows remote attackers to execute arbitrary PHP code via a URL in the classified_path parameter.

    Product
    index.php in SpoonLabs Vivvo Article Management CMS
    Affected
    up to 3.2
    What to do
    Affects up to 3.2. Update index.php in SpoonLabs Vivvo Article Management CMS to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Sep 12, 2006pdf_version.php in SpoonLabs Vivvo Article Management CMS: SQL injectionCVE-2006-4715 · WordPress plugins & themes · reported by MITREHigh 7.5

    SQL injection vulnerability in pdf_version.php in SpoonLabs Vivvo Article Management CMS (aka phpWordPress) 3.2 and earlier allows remote attackers to execute arbitrary SQL commands via the id parameter.

    Product
    pdf_version.php in SpoonLabs Vivvo Article Management CMS
    Affected
    up to 3.2
    What to do
    Affects up to 3.2. Update pdf_version.php in SpoonLabs Vivvo Article Management CMS to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jul 6, 2006index.php in WordPress 2.0.3 allows remote attackers to obtain sensitive information, such as SQL table prefixes, via an invalid paged parameter, which displaysCVE-2006-3389 · WordPress plugins & themes · reported by MITREMedium 5

    index.php in WordPress 2.0.3 allows remote attackers to obtain sensitive information, such as SQL table prefixes, via an invalid paged parameter, which displays the information in an SQL error message. NOTE: this issue has been disputed by a third party who states that the issue does not leak any target-specific information.

    What to do
    Update the plugin to the newest version.
  • Jul 6, 2006WordPress 2.0.3 allows remote attackers to obtain the installation path via a direct request to various files, such as those in the (1) wp-admin, (2) wp-contentCVE-2006-3390 · WordPress plugins & themes · reported by MITREMedium 5

    WordPress 2.0.3 allows remote attackers to obtain the installation path via a direct request to various files, such as those in the (1) wp-admin, (2) wp-content, and (3) wp-includes directories, possibly due to uninitialized variables.

    What to do
    Update the plugin to the newest version.
  • May 30, 2006WordPress 2.0.2 and earlier: Direct static code injectionCVE-2006-2667 · WordPress plugins & themes · reported by MITREHigh 7.5

    Direct static code injection vulnerability in WordPress 2.0.2 and earlier allows remote attackers to execute arbitrary commands by inserting a carriage return and PHP code when updating a profile, which is appended after a special comment sequence into files in (1) wp-content/cache/userlogins/ (2) wp-content/cache/users/ which are later included by cache.php, as demonstrated using the displayname argument.

    Product
    WordPress 2.0.2 and earlier
    Affected
    up to 2.0.2
    What to do
    Affects up to 2.0.2. Update WordPress 2.0.2 and earlier to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Apr 17, 2006Cross-site scripting (XSS) vulnerability in the paging links functionality in template-functions-links.php in Wordpress 1.5.2, and possibly other versions beforCVE-2006-1796 · WordPress plugins & themes · reported by MITREMedium 6.8

    Cross-site scripting (XSS) vulnerability in the paging links functionality in template-functions-links.php in Wordpress 1.5.2, and possibly other versions before 2.0.1, allows remote attackers to inject arbitrary web script or HTML to Internet Explorer users via the request URI ($_SERVER['REQUEST_URI']).

    Fixed in
    2.0.1
    What to do
    Update the plugin to 2.0.1 or newer.
  • Mar 6, 2006WordPress 1.5.2, and possibly other versions before 2.0,: SQL injectionCVE-2006-1012 · WordPress plugins & themes · reported by MITREHigh 7.5

    SQL injection vulnerability in WordPress 1.5.2, and possibly other versions before 2.0, allows remote attackers to execute arbitrary SQL commands via the User-Agent field in an HTTP header for a comment.

    Product
    WordPress 1.5.2, and possibly other versions before 2.0,
    Fixed in
    2.0
    What to do
    Update WordPress 1.5.2, and possibly other versions before 2.0, to 2.0 or newer.
  • Mar 3, 2006Multiple cross-site scripting (XSS) vulnerabilities in the "post comment" functionality of WordPress 2.0.1 and earlier allow remote attackers to inject arbitrarCVE-2006-0985 · WordPress plugins & themes · reported by MITREMedium 4.3

    Multiple cross-site scripting (XSS) vulnerabilities in the "post comment" functionality of WordPress 2.0.1 and earlier allow remote attackers to inject arbitrary web script or HTML via the (1) name, (2) website, and (3) comment parameters.

    Affected
    up to 2.0.1
    What to do
    Affects up to 2.0.1. Update the plugin to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Mar 3, 2006WordPress 2.0.1 and earlier allows remote attackers to obtain sensitive information via a direct request to (1) default-filters.php, (2) template-loader.php, (3CVE-2006-0986 · WordPress plugins & themes · reported by MITREMedium 5

    WordPress 2.0.1 and earlier allows remote attackers to obtain sensitive information via a direct request to (1) default-filters.php, (2) template-loader.php, (3) rss-functions.php, (4) locale.php, (5) wp-db.php, and (6) kses.php in the wp-includes/ directory; and (7) edit-form-advanced.php, (8) admin-functions.php, (9) edit-link-form.php, (10) edit-page-form.php, (11) admin-footer.php, and (12) menu.php in the wp-admin directory; and possibly (13) list directory contents of the wp-includes directory. NOTE: the vars.php, edit-form.php, wp-settings.php, and edit-form-comment.php vectors are already covered by CVE-2005-4463. The menu-header.php vector is already covered by CVE-2005-2110. Other vectors might be covered by CVE-2005-1688. NOTE: if the typical installation of WordPress does not list any site-specific files to wp-includes, then vector [13] is not an exposure.

    Affected
    up to 2.0.1
    What to do
    Affects up to 2.0.1. Update the plugin to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Dec 21, 2005WordPress before 1.5.2 allows remote attackers to obtain sensitive information via a direct request to (1) wp-includes/vars.php, (2) wp-content/plugins/hello.phCVE-2005-4463 · WordPress plugins & themes · reported by MITREMedium 5

    WordPress before 1.5.2 allows remote attackers to obtain sensitive information via a direct request to (1) wp-includes/vars.php, (2) wp-content/plugins/hello.php, (3) wp-admin/upgrade-functions.php, (4) wp-admin/edit-form.php, (5) wp-settings.php, and (6) wp-admin/edit-form-comment.php, which leaks the path in an error message related to undefined functions or failed includes. NOTE: the wp-admin/menu-header.php vector is already covered by CVE-2005-2110. NOTE: the vars.php, edit-form.php, wp-settings.php, and edit-form-comment.php vectors were also reported to affect WordPress 2.0.1.

    Fixed in
    1.5.2
    What to do
    Update the plugin to 1.5.2 or newer.
  • Nov 26, 2005phpWordPress PHP News and Article Manager 3.0: SQL injectionCVE-2005-3844 · WordPress plugins & themes · reported by MITREHigh 7.5

    SQL injection vulnerability in phpWordPress PHP News and Article Manager 3.0 allows remote attackers to execute arbitrary SQL commands via the (1) poll and (2) category parameters to index.php, and (3) the ctg parameter in an archive action.

    Product
    phpWordPress PHP News and Article Manager 3.0
    What to do
    Update phpWordPress PHP News and Article Manager 3.0 to the newest version.
  • Oct 27, 2005The _httpsrequest function in Snoopy 1.2, as used in products such as (1) MagpieRSS, (2) WordPress, (3) Ampache, and (4) Jinzora, allows remote attackers to exeCVE-2005-3330 · WordPress plugins & themes · reported by MITREHigh 7.5

    The _httpsrequest function in Snoopy 1.2, as used in products such as (1) MagpieRSS, (2) WordPress, (3) Ampache, and (4) Jinzora, allows remote attackers to execute arbitrary commands via shell metacharacters in an HTTPS URL to an SSL protected web page, which is not properly handled by the fetch function.

    What to do
    Update the plugin to the newest version.
  • Aug 17, 2005WordPress 1.5.1.3 and earlier: Direct code injectionCVE-2005-2612 · WordPress plugins & themes · reported by MITREHigh 7.5

    Direct code injection vulnerability in WordPress 1.5.1.3 and earlier allows remote attackers to execute arbitrary PHP code via the cache_lastpostdate[server] cookie.

    Product
    WordPress 1.5.1.3 and earlier
    Affected
    up to 1.5.1.3
    What to do
    Affects up to 1.5.1.3. Update WordPress 1.5.1.3 and earlier to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jul 5, 2005PEAR XML_RPC 1.3.0 and earlier: Eval injectionCVE-2005-1921 · WordPress plugins & themes · reported by Red HatHigh 7.5

    Eval injection vulnerability in PEAR XML_RPC 1.3.0 and earlier (aka XML-RPC or xmlrpc) and PHPXMLRPC (aka XML-RPC For PHP or php-xmlrpc) 1.1 and earlier, as used in products such as (1) WordPress, (2) Serendipity, (3) Drupal, (4) egroupware, (5) MailWatch, (6) TikiWiki, (7) phpWebSite, (8) Ampache, and others, allows remote attackers to execute arbitrary PHP code via an XML file, which is not properly sanitized before being used in an eval statement.

    Product
    PEAR XML_RPC 1.3.0 and earlier
    Affected
    up to 1.3.0
    What to do
    Affects up to 1.3.0. Update PEAR XML_RPC 1.3.0 and earlier to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jul 5, 2005XMLRPC server in WordPress 1.5.1.2 and earlier: SQL injectionCVE-2005-2108 · WordPress plugins & themes · reported by MITREHigh 7.5

    SQL injection vulnerability in XMLRPC server in WordPress 1.5.1.2 and earlier allows remote attackers to execute arbitrary SQL commands via input that is not filtered in the HTTP_RAW_POST_DATA variable, which stores the data in an XML file.

    Product
    XMLRPC server in WordPress 1.5.1.2 and earlier
    Affected
    up to 1.5.1.2
    What to do
    Affects up to 1.5.1.2. Update XMLRPC server in WordPress 1.5.1.2 and earlier to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jul 5, 2005WordPress 1.5.1.2 and earlier allows remote attackers to obtain sensitive information via (1) a direct request to menu-header.php or a "1" value in the feed parCVE-2005-2110 · WordPress plugins & themes · reported by MITREMedium 5

    WordPress 1.5.1.2 and earlier allows remote attackers to obtain sensitive information via (1) a direct request to menu-header.php or a "1" value in the feed parameter to (2) wp-atom.php, (3) wp-rss.php, or (4) wp-rss2.php, which reveal the path in an error message. NOTE: vector [1] was later reported to also affect WordPress 2.0.1.

    Affected
    up to 1.5.1.2
    What to do
    Affects up to 1.5.1.2. Update the plugin to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Jun 1, 2005template-functions-category.php in WordPress 1.5.1: SQL injectionCVE-2005-1810 · WordPress plugins & themes · reported by MITREHigh 7.5

    SQL injection vulnerability in template-functions-category.php in WordPress 1.5.1 allows remote attackers to execute arbitrary SQL commands via the $cat_ID variable, as demonstrated using the cat parameter to index.php.

    Product
    template-functions-category.php in WordPress 1.5.1
    What to do
    Update template-functions-category.php in WordPress 1.5.1 to the newest version.
  • May 20, 2005Wordpress 1.5 and earlier allows remote attackers to obtain sensitive information via a direct request to files in (1) wp-content/themes/, (2) wp-includes/, or CVE-2005-1688 · WordPress plugins & themes · reported by MITREMedium 5.3

    Wordpress 1.5 and earlier allows remote attackers to obtain sensitive information via a direct request to files in (1) wp-content/themes/, (2) wp-includes/, or (3) wp-admin/, which reveal the path in an error message.

    Affected
    up to 1.5
    What to do
    Affects up to 1.5. Update the plugin to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 20, 2005wp-trackback.php in Wordpress 1.5 and earlier: SQL injectionCVE-2005-1687 · WordPress plugins & themes · reported by MITREHigh 7.5

    SQL injection vulnerability in wp-trackback.php in Wordpress 1.5 and earlier allows remote attackers to execute arbitrary SQL commands via the tb_id parameter.

    Product
    wp-trackback.php in Wordpress 1.5 and earlier
    Affected
    up to 1.5
    What to do
    Affects up to 1.5. Update wp-trackback.php in Wordpress 1.5 and earlier to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • May 2, 2005Multiple cross-site scripting (XSS) vulnerabilities in template-functions-post.php in WordPress 1.5 and earlier allow remote attackers to execute arbitrary commCVE-2005-1102 · WordPress plugins & themes · reported by MITREMedium 6.8

    Multiple cross-site scripting (XSS) vulnerabilities in template-functions-post.php in WordPress 1.5 and earlier allow remote attackers to execute arbitrary commands via the (1) content or (2) title of the post.

    Affected
    up to 1.5
    What to do
    Affects up to 1.5. Update the plugin to the newest version and check its changelog mentions this fix; if there isn’t one yet, deactivate it until there is.
  • Dec 31, 2004wp-login.php in WordPress 1.2: CRLF injectionCVE-2004-1584 · WordPress plugins & themes · reported by MITREMedium 5

    CRLF injection vulnerability in wp-login.php in WordPress 1.2 allows remote attackers to perform HTTP Response Splitting attacks to modify expected HTML content from the server via the text parameter.

    Product
    wp-login.php in WordPress 1.2
    What to do
    Update wp-login.php in WordPress 1.2 to the newest version.

Where this comes from: the exploited list is CISA’s Known Exploited Vulnerabilities catalog. Everything else is the whole National Vulnerability Database, where each record is published by the team that found the bug (Wordfence, Patchstack, WPScan, the vendors themselves and others); we show who. Exploit odds are FIRST’s EPSS, updated daily. Titles and categories are ours, so check the linked record before acting on a detail. For a write-up of the big ones, see our advisories. Every vendor, and every WordPress plugin and theme with a recorded flaw, also has its own page. All of it is free to reuse as JSON, CSV or RSS.

Weekly security brief

The flaws that hit local websites, every Friday.

One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.

Get in touch

Tell us what you're building.

A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.

01The person who'll do the work writes back
02A short call, then a written plan with the price
03Nothing starts until you say yes
04Hacked or down right now? Call, and we pick up the same day
843-331-6339

Not ready to talk yet? Run the free website check and see what Google sees.

What do you need?
Build
Grow
Protect
Urgent

No newsletter, no sales sequence. Just a reply.