
Auberge · Security record
Is Auberge safe?
No known vulnerability affects the current version (3.0.2). 2 issues were found in earlier versions and fixed, the latest disclosed on May 12, 2015.
Checked today against the WPVulnerability database, for version 3.0.2.
How it’s looked after
- Last release
- Sep 4, 2025 (1 year ago)
- Releases in the last year
- 0
- Active installs
- 1K+
2 known vulnerabilities
- 1 medium
- 1 not rated
None affects the current version.
Every known vulnerability in Auberge
Newest first, with any that affect the current version at the top.
Fixed in 1.4.5 · May 12, 2015 · Patchstack
- medium
Cross-Site Scripting
Fixed in 1.4.5 · CVE-2015-9502 · May 6, 2015 · Wordfence
Questions about Auberge’s security
Is Auberge safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Auberge updated: most attacks target sites that haven’t updated.
Does Auberge have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 2 older issues, fixed in earlier versions, so keep Auberge up to date.
Is Auberge still maintained?
Its last release was 1 year ago, so it may no longer be actively maintained.
Hear about the next one first
Track your theme on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every theme updated.